# CVE-2026-110678: Cpanel::JSON::XS versions before 4.80 for Perl allow memory exhaustion by buffering incremental input past max_size in incr_parse.

> A remote attacker can exhaust process memory in applications using Cpanel::JSON::XS by streaming data that bypasses size limits during incremental parsing.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **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:** AZL-109857, DEBIAN-CVE-2026-110678, GHSA-94qg-48qm-9798, UBUNTU-CVE-2026-110678

## What is CVE-2026-110678?

CVE-2026-110678 is a high-severity denial of service 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 before 4.80 for Perl allow memory exhaustion by buffering incremental input past max_size in incr_parse.

The parser appends each chunk to its buffer. In scalar or list context, it compares max_size with how far it has progressed, not with the buffer length. A chunk that starts with a NUL byte stops the parser before it progresses, and a call in void context skips the check, so the buffer grows without limit.

A peer streaming data to an incr_parse consumer can exhaust process memory regardless of max_size.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

Upgrade to a fixed version.

## Is CVE-2026-110678 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110678 is a high-severity denial of service 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-110678 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-110678/ (Markdown: https://insights.sbomify.com/CVE-2026-110678/index.md)
```

## Sources

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

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