Skip to main content
Menu
CVEs

JSON-XS heap buffer overflow in incremental parser

CVE-2026-129114EUVD-2026-125915GHSA-PMVQ-M677-6P9MPublished November 14, 2026, updated

9.8CriticalCISA-ADP
Exploited
No known exploitation
Fix
Fixed in 4.05
Who is exposed
Not reported

Summary

Earlier releases of JSON::XS for Perl can write one byte past the end of a heap buffer when the incremental parser (incr_parse) appends a one-byte chunk. A peer streaming data to an incr_parse consumer can trigger this by choosing how the input is split into reads.

Written by a model

Original 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.

What to do

Upgrade to a fixed version: 4.05.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by 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), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129114 (entry last updated 2026-11-17):
Affected:
- JSON-XS: from 3.04, fixed in 4.05
Fixed versions: 4.05.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129114 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129114 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://metacpan.org/release/MLEHMANN/JSON-XS-4.05/changes
- https://www.cve.org/CVERecord?id=CVE-2026-129114
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129114
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129114"}.

Affected versions

cve.now Index

30of 100 · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 35 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now3 days
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  4. Record last updated
  5. Posted on X by cve.now

Public exploit activity

100%0Posted on X by cve.nowNov 14Nov 22
  • EPSS: 0.44%
  • Posted on X by cve.now Nov 17

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

On X 1

Evidence 3

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129114
RecordNVD · CVE-2026-129114
Other links 1
Linkmetacpan.org · release/MLEHMANN/JSON-XS-4.05/changes

Questions about CVE-2026-129114

Is CVE-2026-129114 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-129114?

JSON-XS: from 3.04 before 4.05.

Source: cve.now feed data

How do I fix CVE-2026-129114?

Upgrade to JSON-XS 4.05 or later.

Source: cve.org

No corrections so far. Something wrong on this page? Report an error.