JSON-XS · CWE-193 · CWE-122 · published 2026-11-14
CVE-2026-129114JSON::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
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-129114 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 35% of all CVEs. This JSON-XS vulnerability: CVSS 9.8 (v3.1), attacks can be automated, a successful attack gives total control of the component. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (36th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.8 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-193: Off-by-one Error · CWE-122: Heap-based Buffer Overflow
Affected versions (from the CVE record)#
- JSON-XS
3.04to before4.05(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.