# CVE-2026-129114: JSON::XS versions from 3.04 before 4.05 for Perl write one byte past a heap buffer when appending a one-byte chunk in incr_parse.

> A streaming peer can trigger a one-byte heap out-of-bounds write in JSON::XS incremental parsing, affecting Perl apps using incr_parse.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** Yes (`incr_parse`)
- **Fix available:** No
- **Published:** 14 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-129114, GHSA-pmvq-m677-6p9m, UBUNTU-CVE-2026-129114

## What is CVE-2026-129114?

CVE-2026-129114 is a critical memory corruption vulnerability, published on 14 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

JSON::XS versions from 3.04 before 4.05 for Perl write one byte past a heap buffer when appending a one-byte chunk in incr_parse.

The incremental buffer grows to one and a half times the length it must hold, with no room reserved for the terminating NUL. For an empty buffer and a one-byte chunk that request is one byte, which a buffer whose front was removed by earlier decodes can already have, so nothing is reallocated and the NUL lands one byte past the allocation.

A peer streaming data to an incr_parse consumer, choosing how the input is split into reads, can cause a one-byte heap out-of-bounds write.

Weakness: CWE-193 (Off-by-one Error), CWE-122 (Heap-based Buffer Overflow)

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

An affected version is only exploitable if your software calls incr_parse. Many projects that include it are not exposed.


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

No fix has been published for CVE-2026-129114 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-129114 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129114 is a critical memory corruption vulnerability, published on 14 Nov 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-129114 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software calls incr_parse. Many projects that include it are not exposed.

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.
   If an affected version is present, also search the code for calls to incr_parse and report whether any exist.
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-129114/ (Markdown: https://insights.sbomify.com/CVE-2026-129114/index.md)
```

## Sources

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

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