Skip to main content
VulnerabilityPublished Updated

CVE-2026-110673: Cpanel::JSON::XS versions before 4.80 for Perl allow stack exhaustion via nested tagged values under

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-110673· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 4.80 soon.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.17.5
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.80
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade Cpanel-JSON-XS (Perl module) to 4.80.

Affected software

ProductAffectedFixed in
Cpanel-JSON-XSAffected
  • <4.80
Fixed in
  • 4.80
CPANCpanel-JSON-XSpkg:cpan/Cpanel-JSON-XSOther threatsAffected
  • <4.80
Fixed in
  • 4.80

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

Cpanel::JSON::XS versions before 4.80 for Perl allow stack exhaustion via nested tagged values under allow_tags in decode_tag. With allow_tags, "(" starts a tagged value. Its tag and value are decoded recursively, and each can start another tagged value. Unlike arrays and objects, this nesting is not counted against max_depth. A run of "(" bytes exhausts the C stack and triggers an uncatchable segmentation fault regardless of max_depth.

References

Community reviews

Loading reviews…