cve.bz

CVE-2026-110676

7.5 highEPSS 0.5%

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

On this page
Cpanel::JSON::XS versions before 4.80 for Perl allow memory exhaustion by encoding exponent notation as full decimal digits under allow_bignum. With allow_bignum, a JSON number with a fraction or exponent decodes to a Math::BigFloat, which stores the exponent separately and so decodes cheaply. Encoding it untyped or as JSON_TYPE_FLOAT writes the plain decimal form with one digit per unit of exponent. Nothing bounds the exponent, so the 12-byte text [1e30000000] encodes to 30 MB. Untrusted JSON decoded with allow_bignum and encoded again can exhaust memory and CPU.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 42nd 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-405 Asymmetric Resource Consumption (Amplification)
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-110676 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110676?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110676?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-110676 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-110676
Debian14libcpanel-json-xs-perl4.80-1DEBIAN-CVE-2026-110676
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morelibcpanel-json-xs-perlno fix listedUBUNTU-CVE-2026-110676
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
Azure Linux3perl-Cpanel-JSON-XSno fix listedAZL-109845

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.

References

Check your stackJSON