CVE-20XX-?
agent?

Critical, and still unpatched.

Critical-severity CVEs with no patch or advisory linked yet. These are the ones to watch.

3 CVEs · updated 2026-11-19 03:22 UTC

Reset all
  1. 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. 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.

    Memory safety Library

    9.8 CRITICAL 0.4% exploit odds No fix listed
  2. CVE-2026-129115

    JSON::XS versions from 3.0 before 4.05 for Perl read freed stack memory when a FREEZE result's serialisation grows the Perl stack under allow_tags in encode_rv. With allow_tags, an object's FREEZE method is called in list context and each returned value is encoded through a saved Perl stack pointer. When encoding a returned value calls back into Perl, through TO_JSON under convert_blessed or another FREEZE, and that callback grows the stack, the stack is reallocated while the saved pointer still refers to the freed block. Encoding such objects reads freed memory, and encode can return undef without an error.

    Memory safety Library

    9.1 CRITICAL 0.4% exploit odds No fix listed
  3. 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. 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.

    Memory safety Library

    9.1 CRITICAL 0.4% exploit odds No fix listed

Critical CVEs are vulnerabilities scored 9.0 or higher on the CVSS scale. This list shows the ones with no patch or vendor advisory linked yet, ranked by how likely they are to be exploited (EPSS).