cve.bz

CVE-2026-129113 JSON::XS versions from 4.0_00 before 4.05 for Perl corrupt the incremental buffer length by chopping past its end in incr_skip after a top-level number

no score yet

No CVSS score yet.

On this page
JSON::XS versions from 4.0_00 before 4.05 for Perl corrupt the incremental buffer length by chopping past its end in incr_skip after a top-level number. The incremental parser scans any run of digits, signs, dots and exponent markers as one number, but the decoder stops at the end of a valid number, so the parser keeps an offset into bytes it has not decoded. It then empties the buffer without clearing those bytes, and a later incr_parse call without new input reads them again and moves the offset past the end of the buffer. incr_skip, the documented recovery after an error, removes that many bytes and the buffer length wraps. A peer sending input such as "1-2" to an incr_parse consumer can make the next read of incr_text exit the process through perl's uncatchable out-of-memory path.
CWE
CWE-191 Integer Underflow (Wrap or Wraparound)
Published
Assigned by
CPANSec (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-129113 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-129113?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-129113?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-129113 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-129113

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-129113](https://cve.bz/cve/badge/CVE-2026-129113.svg)](https://cve.bz/cve/CVE-2026-129113)

HTML:

<a href="https://cve.bz/cve/CVE-2026-129113"><img src="https://cve.bz/cve/badge/CVE-2026-129113.svg" alt="CVE-2026-129113"></a>

Versions

From the CNA's record in the CVE List.

ProductAffected
JSON-XSfrom 4.0_00 before 4.05

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14libjson-xs-perlno fix listedDEBIAN-CVE-2026-129113

From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

References

Check your stackJSON