CVE-2026-124536: JSON::XS versions before 4.05 for Perl allow memory exhaustion by buffering incremental input past
Source GCVE Database
Not known to be exploited : upgrade to 4.05 soon.
Data as of 14 Nov 2026, 13:18 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 4.05
Exploitation evidence
Disclosed: evidence found.
CVE published 14 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade JSON-XS (Perl module) to 4.05.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| JSON-XS | Affected
| Fixed in
|
CPANJSON-XSpkg:cpan/JSON-XSOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade to JSON::XS version 4.05 or later once available, as the vulnerability affects versions before 4.05. Until then, consider limiting exposure to untrusted incremental JSON input streams or applying application-level input validation to mitigate memory exhaustion risks.
Description
JSON::XS versions before 4.05 for Perl have a vulnerability in the incremental parser (incr_parse) that allows memory exhaustion. The parser buffers input chunks and incorrectly handles NUL bytes, causing the buffer to grow beyond the configured max_size limit. This can lead to process memory exhaustion when processing crafted input streams.