cve.bz

CVE-2026-110687 Improper Handling of Unicode Encoding

7.5 highEPSS 0.4%

High (7.5). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Cpanel::JSON::XS versions from 4.43 before 4.80 for Perl misorder byte-string keys during canonical encoding in utf16_cmp. 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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 37th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-176 Improper Handling of Unicode Encoding
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-110687 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110687?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110687?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-110687 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13libcpanel-json-xs-perlno fix listedDEBIAN-CVE-2026-110687
Debian14libcpanel-json-xs-perl4.80-1DEBIAN-CVE-2026-110687
SUSELinux Enterprise Module for Package Hub 15 SP7perl-Cpanel-JSON-XS4.800.0-150700.3.9.1SUSE-SU-2026:4926-1
openSUSELeap 16.0perl-Cpanel-JSON-XS4.800.0-bp160.1.1openSUSE-SU-2026:22187-1
openSUSETumbleweedperl-Cpanel-JSON-XS4.800.0-1.1openSUSE-SU-2026:12217-1

From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · SUSE · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON