<?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://cve.radiocsirt.org</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>Tue, 06 Oct 2026 18:29:56 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-374889</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-374889</link>
      <description>EUVD-2026-374889</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-374889</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72705</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72705</link>
      <description>&lt;p&gt;The guard checker in Rocq Prover does not follow recursive calls made through a fixpoint&amp;#39;s own arguments. A fixpoint may pass itself as a higher-order argument to a second fixpoint, which then applies it to a value that is not a subterm of the structural argument. Passing the recursive function to a plain definition is rejected because the checker unfolds the definition and observes the call, but passing it to a fixpoint is accepted because higher-order recursive calls through fixpoint arguments are not tracked. This admits a type that is definitionally equal to its own negation, so self-application produces False in purely definitional code, without tactics, axioms, plugins or unsafe flags, and Print Assumptions reports the result as closed under the global context. Fixed in Rocq 9.2.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The guard checker in Rocq Prover does not follow recursive calls made through a fixpoint&amp;#39;s own arguments. A fixpoint may pass itself as a higher-order argument to a second fixpoint, which then applies it to a value that is not a subterm of the structural argument. Passing the recursive function to a plain definition is rejected because the checker unfolds the definition and observes the call, but passing it to a fixpoint is accepted because higher-order recursive calls through fixpoint arguments are not tracked. This admits a type that is definitionally equal to its own negation, so self-application produces False in purely definitional code, without tactics, axioms, plugins or unsafe flags, and Print Assumptions reports the result as closed under the global context. Fixed in Rocq 9.2.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72705</guid>
    </item>
    <item>
      <title>GHSA-f4rc-7978-q94g</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f4rc-7978-q94g</link>
      <description>&lt;p&gt;The guard checker in Rocq Prover does not follow recursive calls made through a fixpoint&amp;#39;s own arguments. A fixpoint may pass itself as a higher-order argument to a second fixpoint, which then applies it to a value that is not a subterm of the structural argument. Passing the recursive function to a plain definition is rejected because the checker unfolds the definition and observes the call, but passing it to a fixpoint is accepted because higher-order recursive calls through fixpoint arguments are not tracked. This admits a type that is definitionally equal to its own negation, so self-application produces False in purely definitional code, without tactics, axioms, plugins or unsafe flags, and Print Assumptions reports the result as closed under the global context. Fixed in Rocq 9.2.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The guard checker in Rocq Prover does not follow recursive calls made through a fixpoint&amp;#39;s own arguments. A fixpoint may pass itself as a higher-order argument to a second fixpoint, which then applies it to a value that is not a subterm of the structural argument. Passing the recursive function to a plain definition is rejected because the checker unfolds the definition and observes the call, but passing it to a fixpoint is accepted because higher-order recursive calls through fixpoint arguments are not tracked. This admits a type that is definitionally equal to its own negation, so self-application produces False in purely definitional code, without tactics, axioms, plugins or unsafe flags, and Print Assumptions reports the result as closed under the global context. Fixed in Rocq 9.2.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f4rc-7978-q94g</guid>
    </item>
  </channel>
</rss>
