CVE-2026-110688: Libcpanel json xs perl · Cpanel::JSON::XS versions from 4.51 before 4.80 for Perl allow quadratic CPU
Affects libcpanel-json-xs-perlSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 22:31 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10libcpanel-json-xs-perlpkg:deb/ubuntu/libcpanel-json-xs-perl?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlibcpanel-json-xs-perlpkg:deb/ubuntu/libcpanel-json-xs-perl?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlibcpanel-json-xs-perlpkg:deb/ubuntu/libcpanel-json-xs-perl?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSlibcpanel-json-xs-perlpkg:deb/ubuntu/libcpanel-json-xs-perl?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 20.04 LTSlibcpanel-json-xs-perlpkg:deb/ubuntu/libcpanel-json-xs-perl?arch=source&distro=focalOther threats | Affected
| Fixed in– |
Ubuntu 18.04 LTSlibcpanel-json-xs-perlpkg:deb/ubuntu/libcpanel-json-xs-perl?arch=source&distro=bionicOther threats | Affected
| Fixed in– |
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 from 4.51 before 4.80 for Perl allow quadratic CPU use by revalidating the remaining buffer per value in incr_parse. At the first non-ASCII byte in a string, the decoder validates UTF-8 from there to the end of its input. incr_parse decodes each buffered value with a fresh decoder, so every value revalidates the rest of the buffer, and doubling the input quadruples the work. A peer that sends about a megabyte of ordinary non-ASCII JSON in one read ties up the process for seconds of CPU time.