<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 23:18:15 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-85644</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-85644</link>
      <description>&lt;p&gt;XS::Parse::Infix versions from 0.40 through 0.49 for Perl treat a number as an array reference.&lt;/p&gt;
&lt;p&gt;The wrapper function XS::Parse::Infix generates for a list-associative infix operator checks whether arguments are array references, but it tests using SvRV() rather than SvROK(). SvRV() reads a union slot that only holds a referent once SvROK(sv) is true, so the guard never validates that it is a reference. For an IV or NV that slot holds the number itself, SvRV() returns the caller&amp;#39;s value and SvTYPE() dereferences it at offset 12. This will generally result in a segmentation fault.&lt;/p&gt;
&lt;p&gt;An application that hands the wrapper a list built from decoded input (for example, from JSON) lets whoever supplies a number in that list choose the address that the interpreter dereferences.&lt;/p&gt;
&lt;p&gt;An ordinary string&amp;#39;s byte 12 is rarely SVt_PVAV so the guard croaks by luck, but an attacker-crafted string carrying 0x0b there passes, and the buffer is then used as an AV head, with AvARRAY taken from bytes 16-23 and its entries pushed onto the Perl stack as live SVs.&lt;/p&gt;
&lt;p&gt;A simple proof-of-concept uses the zip operator:&lt;/p&gt;
&lt;p&gt;use Syntax::Operator::Zip &amp;#39;zip&amp;#39;;&lt;/p&gt;
&lt;p&gt;my @args = ([1], 2);
    zip(@args);&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;XS::Parse::Infix versions from 0.40 through 0.49 for Perl treat a number as an array reference.&lt;/p&gt;
&lt;p&gt;The wrapper function XS::Parse::Infix generates for a list-associative infix operator checks whether arguments are array references, but it tests using SvRV() rather than SvROK(). SvRV() reads a union slot that only holds a referent once SvROK(sv) is true, so the guard never validates that it is a reference. For an IV or NV that slot holds the number itself, SvRV() returns the caller&amp;#39;s value and SvTYPE() dereferences it at offset 12. This will generally result in a segmentation fault.&lt;/p&gt;
&lt;p&gt;An application that hands the wrapper a list built from decoded input (for example, from JSON) lets whoever supplies a number in that list choose the address that the interpreter dereferences.&lt;/p&gt;
&lt;p&gt;An ordinary string&amp;#39;s byte 12 is rarely SVt_PVAV so the guard croaks by luck, but an attacker-crafted string carrying 0x0b there passes, and the buffer is then used as an AV head, with AvARRAY taken from bytes 16-23 and its entries pushed onto the Perl stack as live SVs.&lt;/p&gt;
&lt;p&gt;A simple proof-of-concept uses the zip operator:&lt;/p&gt;
&lt;p&gt;use Syntax::Operator::Zip &amp;#39;zip&amp;#39;;&lt;/p&gt;
&lt;p&gt;my @args = ([1], 2);
    zip(@args);&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-85644</guid>
    </item>
    <item>
      <title>GHSA-ch9g-92vf-wwhv</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-ch9g-92vf-wwhv</link>
      <description>&lt;p&gt;XS::Parse::Infix versions from 0.40 through 0.49 for Perl treat a number as an array reference.&lt;/p&gt;
&lt;p&gt;The wrapper function XS::Parse::Infix generates for a list-associative infix operator checks whether arguments are array references, but it tests using SvRV() rather than SvROK(). SvRV() reads a union slot that only holds a referent once SvROK(sv) is true, so the guard never validates that it is a reference. For an IV or NV that slot holds the number itself, SvRV() returns the caller&amp;#39;s value and SvTYPE() dereferences it at offset 12. This will generally result in a segmentation fault.&lt;/p&gt;
&lt;p&gt;An application that hands the wrapper a list built from decoded input (for example, from JSON) lets whoever supplies a number in that list choose the address that the interpreter dereferences.&lt;/p&gt;
&lt;p&gt;An ordinary string&amp;#39;s byte 12 is rarely SVt_PVAV so the guard croaks by luck, but an attacker-crafted string carrying 0x0b there passes, and the buffer is then used as an AV head, with AvARRAY taken from bytes 16-23 and its entries pushed onto the Perl stack as live SVs.&lt;/p&gt;
&lt;p&gt;A simple proof-of-concept uses the zip operator:&lt;/p&gt;
&lt;p&gt;use Syntax::Operator::Zip &amp;#39;zip&amp;#39;;&lt;/p&gt;
&lt;p&gt;my @args = ([1], 2);
    zip(@args);&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;XS::Parse::Infix versions from 0.40 through 0.49 for Perl treat a number as an array reference.&lt;/p&gt;
&lt;p&gt;The wrapper function XS::Parse::Infix generates for a list-associative infix operator checks whether arguments are array references, but it tests using SvRV() rather than SvROK(). SvRV() reads a union slot that only holds a referent once SvROK(sv) is true, so the guard never validates that it is a reference. For an IV or NV that slot holds the number itself, SvRV() returns the caller&amp;#39;s value and SvTYPE() dereferences it at offset 12. This will generally result in a segmentation fault.&lt;/p&gt;
&lt;p&gt;An application that hands the wrapper a list built from decoded input (for example, from JSON) lets whoever supplies a number in that list choose the address that the interpreter dereferences.&lt;/p&gt;
&lt;p&gt;An ordinary string&amp;#39;s byte 12 is rarely SVt_PVAV so the guard croaks by luck, but an attacker-crafted string carrying 0x0b there passes, and the buffer is then used as an AV head, with AvARRAY taken from bytes 16-23 and its entries pushed onto the Perl stack as live SVs.&lt;/p&gt;
&lt;p&gt;A simple proof-of-concept uses the zip operator:&lt;/p&gt;
&lt;p&gt;use Syntax::Operator::Zip &amp;#39;zip&amp;#39;;&lt;/p&gt;
&lt;p&gt;my @args = ([1], 2);
    zip(@args);&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-ch9g-92vf-wwhv</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11863-1 — perl-XS-Parse-Keyword-0.500.0-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11863-1</link>
      <description>&lt;p&gt;perl-XS-Parse-Keyword-0.500.0-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;perl-XS-Parse-Keyword-0.500.0-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11863-1</guid>
    </item>
  </channel>
</rss>
