<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T07:51:54.288723+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-406618</id>
    <title>EUVD-2026-406618</title>
    <updated>2026-11-17T07:51:54.291063+00:00</updated>
    <content>EUVD-2026-406618</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-406618"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4q52-849c-cv9p</id>
    <title>GHSA-4q52-849c-cv9p</title>
    <updated>2026-11-17T07:51:54.291091+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>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.</p>
<p>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.</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4q52-849c-cv9p"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-129113</id>
    <title>UBUNTU-CVE-2026-129113</title>
    <updated>2026-11-17T07:51:54.291122+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:14.04:LTS: libjson-xs-perl, Ubuntu:16.04:LTS: libjson-xs-perl, Ubuntu:18.04:LTS: libjson-xs-perl, Ubuntu:20.04:LTS: libjson-xs-perl, Ubuntu:22.04:LTS: libjson-xs-perl, Ubuntu:24.04:LTS: libjson-xs-perl, Ubuntu:26.10: libjson-xs-perl, Ubuntu:26.04:LTS: libjson-xs-perl</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-129113"/>
  </entry>
</feed>
