CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HHigh (7.5). EPSS 0.5% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExplain CVE-2026-110680 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110680?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110680?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-110680 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.
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | libcpanel-json-xs-perl | no fix listed | DEBIAN-CVE-2026-110680 |
| Debian | 14 | libcpanel-json-xs-perl | 4.80-1 | DEBIAN-CVE-2026-110680 |
| Ubuntu | 22.04:LTS, 24.04:LTS, 26.04:LTS and 1 more | libcpanel-json-xs-perl | no fix listed | UBUNTU-CVE-2026-110680 |
| SUSE | Linux Enterprise Module for Package Hub 15 SP7 | perl-Cpanel-JSON-XS | 4.800.0-150700.3.9.1 | SUSE-SU-2026:4926-1 |
| openSUSE | Leap 16.0 | perl-Cpanel-JSON-XS | 4.800.0-bp160.1.1 | openSUSE-SU-2026:22187-1 |
| openSUSE | Tumbleweed | perl-Cpanel-JSON-XS | 4.800.0-1.1 | openSUSE-SU-2026:12217-1 |
| Azure Linux | 3 | perl-Cpanel-JSON-XS | no fix listed | AZL-109866 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.
Red Hat rates this Important.
Red Hat has rated this vulnerability as Important because an out-of-bounds write can corrupt heap or stack memory, potentially leading to arbitrary code execution or process crashes. Exploitation requires specific application design preconditions, namely that canonical encoding is enabled while a tied or thread-shared hash is modified concurrently by another thread or tied method during serialization. Standard Perl workloads that process thread-isolated hashes or do not rely on canonical sorting are unaffected.
--- CME Mitigation Guidance (2026-10-20) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to enforce boundary verification or prohibit dynamic modification of tied and threads::shared hashes during canonical JSON encoding in Cpanel::JSON::XS: upgrade to Cpanel::JSON::XS 4.80 (or the fixed Perl Cpanel Json Xs builds), which croak with an unstable hash key count error when the iteration index reaches or exceeds the allocated key limit, closing all 2 injection vectors (dynamic expansion of a tied hash during key iteration, concurrent key insertion into a threads::shared hash during encoding). Until patched, this is a concern on Applications using Cpanel::JSON::XS with canonical sorting enabled on tied or threads::shared hashes, so Disable canonical sorting or ensure mutual exclusion so tied or threads::shared hashes cannot grow or receive new keys while being encoded. As a compensating measure, Enable ASLR to randomize process memory layout and hinder reliable exploitation of stack or heap corruption, Enable Full RELRO and PIE to prevent Global Offset Table overwrites and randomize code offsets, Deploy Control Flow Integrity or Shadow Call Stack to detect and block execution hijacking if corrupted memory alters return addresses or function pointers, and Configure service watchdogs with automatic restart using systemd WatchdogSec and Restart to recover if a crash occurs. These controls limit blast radius and contain exploitation, but they do not fix the underlying out-of-bounds write defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-1204 Service Watchdog and Automatic Restart (systemd WatchdogSec/Restart) (medium)
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-110680.