CVE and update status of the FreeBSD ports tree3,924 unaddressed CVEs in 706 portsAll times are CET
CVE details

CVE-2026-124536

JSON::XS versions before 4.05 for Perl allow memory exhaustion by buffering incremental input past max_size after a NUL byte in incr_parse. The parser appends each chunk to its buffer and compares max_size with how far it has progressed, not with the buffer length. It treats a NUL byte as the end of the input, so a NUL within the first max_size bytes keeps it short of the limit. The buffer keeps growing, and incr_skip cannot remove the NUL. A peer streaming data to an incr_parse consumer can exhaust process memory regardless of max_size.

Score
–
Published
2026-11-14
Links
NVD · cve.org · Report wrong data

Matched ports (1)

PortPackageVersionStatusMaintainer
converters/p5-JSON-XSp5-JSON-XS4.04unaddressedsunpoet@FreeBSD.org

Template for a VuXML entry

Check the content

Check the version numbers before you commit this entry. Some ports share an entry in the CVE database with another port, such as sqlite2 and sqlite3. The version shown here may then be one that never existed for this port.

Ranges per package from the CVE rows that match this port, in pkg notation with the port's epoch and revision, every bound checked with pkg; one range per epoch the port actually had. make newentry in security/vuxml creates the vid.

No CPE in the port Makefile

converters/p5-JSON-XS (CPE matched by the package name) has no USES=cpe. The CVE was matched through a CPE from another source, so the package and the version range may belong to a different product. Check the CVE record before using this entry.

  <vuln vid="FIXME (make newentry)">
    <topic>p5-JSON-XS -- FIXME</topic>
    <affects>
      <package>
	<name>p5-JSON-XS</name>
	<range><lt>4.05</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>CVE-2026-124536: JSON::XS versions before 4.05 for Perl allow memory
	  exhaustion by buffering incremental input past max_size after a NUL
	  byte in incr_parse. The parser appends each chunk to its buffer and
	  compares max_size with how far it has progressed, not with the
	  buffer length. It treats a NUL byte as the end of the input, so a
	  NUL within the first max_size bytes keeps it short of the limit.
	  The buffer keeps growing, and incr_skip cannot remove the NUL. A
	  peer streaming data to an incr_parse consumer can exhaust process
	  memory regardless of max_size.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-124536</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-124536</url>
    </references>
    <dates>
      <discovery>2026-11-14</discovery>
      <entry>2026-11-15</entry>
    </dates>
  </vuln>