UBUNTU-CVE-2026-110672: High severity ubuntu/libcpanel-json-xs-perl vulnerability
Cpanel::JSON::XS versions before 4.80 for Perl leak the decoded key of an object rejected for a duplicate key or a missing colon in decodehv. A quoted key of 24 or more bytes, or one containing a non-ASCII byte or an escape sequence, is decoded into a new scalar. Nothing frees that scalar when the object is rejected for a missing ':' after the key or, from 4.09, for a duplicate key. Duplicate keys are an error unless allowdupkeys, dupkeysasarrayref or relaxed is set. A process that keeps running after a failed decode retains one key per rejected document, with its size chosen by the sender. Repeated requests exhaust process memory.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/libcpanel-json-xs-perlto a version that resolves this vulnerability.Fixed in 3.0210-1ubuntu1+esm1 - Upgrade
Upgrade
ubuntu/libcpanel-json-xs-perlto a version that resolves this vulnerability.Fixed in 3.0239-1ubuntu0.1~esm1 - Upgrade
Upgrade
ubuntu/libcpanel-json-xs-perlto a version that resolves this vulnerability.Fixed in 4.19-1ubuntu0.1+esm1 - Upgrade
Upgrade
ubuntu/libcpanel-json-xs-perlto a version that resolves this vulnerability.Fixed in 4.27-1ubuntu0.3 - Upgrade
Upgrade
ubuntu/libcpanel-json-xs-perlto a version that resolves this vulnerability.Fixed in 4.37-1ubuntu0.2 - Upgrade
Upgrade
ubuntu/libcpanel-json-xs-perlto a version that resolves this vulnerability.Fixed in 4.42-1ubuntu0.1 - Upgrade
Upgrade
ubuntu/libcpanel-json-xs-perlto a version that resolves this vulnerability.Fixed in 4.40-1ubuntu0.1 - Upgrade
Upgrade
Cpanel::JSON::XSto a version that resolves this vulnerability.Fixed in 4.80
Event History
Frequently Asked Questions
Which deployments are realistically exposed to memory exhaustion?
Long-running processes that decode attacker-controlled JSON are exposed if they continue running after a decode failure. Each rejected document can retain one decoded key, and the sender can choose that key's size.
What does an attacker need to send to trigger the leak?
The attacker needs to submit JSON containing an object that is rejected after processing a quoted key, such as a key followed by no colon. Duplicate-key rejections can also trigger the issue from version 4.09 onward; the quoted key must be at least 24 bytes, contain a non-ASCII byte, or contain an escape sequence.
Are duplicate-key errors enabled by default?
Yes. Duplicate keys are errors unless allow_dupkeys, dupkeys_as_arrayref, or relaxed is enabled, so the duplicate-key rejection path affects the default behavior.