# CVE-2026-110672: Cpanel::JSON::XS versions before 4.80 for Perl leak the decoded key of an object rejected for a duplicate key or a missing colon in decode_hv.

> A memory leak in Cpanel::JSON::XS allows attackers to exhaust process memory by sending malformed JSON, causing denial of service.

- **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-109854, DEBIAN-CVE-2026-110672, GHSA-cg4x-76pf-wq6q, UBUNTU-CVE-2026-110672

## What is CVE-2026-110672?

CVE-2026-110672 is a high-severity memory corruption 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 leak the decoded key of an object rejected for a duplicate key or a missing colon in decode_hv.

A quoted key of 24 or more bytes, or one containing a non-ASCII byte or an escape sequence, is decoded into a new scalar. Nothing frees that scalar when the object is rejected for a missing ':' after the key or, from 4.09, for a duplicate key. Duplicate keys are an error unless allow_dupkeys, dupkeys_as_arrayref or relaxed is set.

A process that keeps running after a failed decode retains one key per rejected document, with its size chosen by the sender. Repeated requests exhaust process memory.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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


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

Upgrade to a fixed version.

## Is CVE-2026-110672 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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