CVE-2026-110687: Cpanel::JSON::XS versions from 4.43 before 4.80 for Perl misorder byte-string keys during canonical encoding in utf16_cmp

Published Oct 19, 2026
·
Updated

Cpanel::JSON::XS versions from 4.43 before 4.80 for Perl misorder byte-string keys during canonical encoding in utf16cmp. canonical sorts keys by UTF-16 code units. When any key in a hash is UTF-8 flagged, every key is decoded as UTF-8 for the comparison, including byte-string keys that the encoder writes out as Latin-1 characters. A byte-string key whose bytes are valid UTF-8 is sorted out of order, and two keys that encode differently can compare equal and are left in hash order. The same data can encode to different canonical documents across processes.

Affected Software

12 affected componentsFixes available
cpan/Cpanel-JSON-XS>=4.43<4.80
ubuntu/libcpanel-json-xs-perl*
ubuntu/libcpanel-json-xs-perl*
ubuntu/libcpanel-json-xs-perl*
ubuntu/libcpanel-json-xs-perl*
ubuntu/libcpanel-json-xs-perl*
ubuntu/libcpanel-json-xs-perl*
ubuntu/libcpanel-json-xs-perl*
debian/libcpanel-json-xs-perl<=4.35-1+deb12u1, <=4.39-2~deb13u1
4.80-1
debian/libcpanel-json-xs-perl*
debian/libcpanel-json-xs-perl*
debian/libcpanel-json-xs-perl<4.80-1
4.80-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/libcpanel-json-xs-perl to a version that resolves this vulnerability.

    Fixed in 4.80-1
  2. Upgrade

    Upgrade Cpanel-JSON-XS to a version that resolves this vulnerability.

    Fixed in 4.80

Event History

Oct 19, 2026
CVE Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·06:12 PM
Data Sourced
via MITRE·06:12 PM
RemedyDescriptionWeakness
Data Sourced
via OSV·06:12 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness
Oct 31, 2026
Data Sourced
via OSV·03:30 AM
Affected Software

Frequently Asked Questions

1

Which releases contain the issue, and what version fixes it?

Cpanel::JSON::XS versions from 4.43 up to, but not including, 4.80 are affected. Version 4.80 contains the fix.

2

When can an application trigger the incorrect ordering?

The application must use canonical encoding on a hash that includes at least one UTF-8-flagged key and a byte-string key whose bytes are valid UTF-8. The byte-string key is written as Latin-1 but is treated as UTF-8 during the sort comparison.

3

Are applications that do not use canonical encoding affected?

The described behavior occurs during canonical encoding in utf16_cmp. The provided information does not identify an effect outside canonical encoding.

4

How can I determine whether this affects output consistency?

Check whether the application uses an affected version and canonically encodes hashes containing mixed UTF-8-flagged and byte-string keys. Under those conditions, differently encoded keys can compare equal and output can vary with hash order across processes.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203