# CVE-2026-110682: Cpanel::JSON::XS versions from 4.42 before 4.80 for Perl let input chunking change the decoded value of top-level numbers in incr_parse.

> Attackers can manipulate JSON stream decoding by controlling read boundaries, altering decoded values and message counts in Perl applications.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-110682, GHSA-vg22-xr3v-rw3m, UBUNTU-CVE-2026-110682

## What is CVE-2026-110682?

CVE-2026-110682 is a high-severity vulnerability, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cpanel::JSON::XS versions from 4.42 before 4.80 for Perl let input chunking change the decoded value of top-level numbers in incr_parse.

allow_nonref is enabled by default and incr_parse inherits it. A top-level number, true, false or null has no closing delimiter, so the incremental parser decodes whatever has arrived. The bytes 12 decode as one value when read together, but as 1 and then 2 when split across two reads.

A peer that can influence read boundaries can change how many messages a stream consumer decodes and what values they carry.

Weakness: CWE-436 (Interpretation Conflict)

## Which versions are affected by CVE-2026-110682?


## How do I fix CVE-2026-110682?

Upgrade to a fixed version.

## Is CVE-2026-110682 being exploited?

There is no known exploitation of CVE-2026-110682 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-110682 and fix it if it is affected.

What it is: CVE-2026-110682 is a high-severity vulnerability, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110682 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-110682/ (Markdown: https://insights.sbomify.com/CVE-2026-110682/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-110682
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-110682
- OSV: https://osv.dev/vulnerability/CVE-2026-110682

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-110682/
Summaries are generated and may contain mistakes; the official description above is the record.