<?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>Sun, 22 Nov 2026 22:09:54 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-409066</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-409066</link>
      <description>EUVD-2026-409066</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-409066</guid>
    </item>
    <item>
      <title>fkie_cve-2026-71500</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-71500</link>
      <description>&lt;p&gt;Mareforma is a local verification layer for AI-assisted research. From 0.3.0 until 0.3.8, _maybe_update_replicated_unlocked in mareforma/db/core.py does not check t_invalid in its new-claim gate, peer-selection query, or final update, so a claim marked invalid by a signed contradiction verdict can still be promoted to REPLICATED through convergence. The invalidated claim can also act as the corroborating peer that promotes an honest claim, bypassing the trust ladder&amp;#39;s terminal refutation state. This issue is fixed in version 0.3.8.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Mareforma is a local verification layer for AI-assisted research. From 0.3.0 until 0.3.8, _maybe_update_replicated_unlocked in mareforma/db/core.py does not check t_invalid in its new-claim gate, peer-selection query, or final update, so a claim marked invalid by a signed contradiction verdict can still be promoted to REPLICATED through convergence. The invalidated claim can also act as the corroborating peer that promotes an honest claim, bypassing the trust ladder&amp;#39;s terminal refutation state. This issue is fixed in version 0.3.8.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-71500</guid>
    </item>
    <item>
      <title>GHSA-rgg9-956j-3378 — Mareforma: invalidated claims still promote to REPLICATED</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rgg9-956j-3378</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mareforma&lt;/p&gt;
&lt;p&gt;## What&amp;#39;s wrong&lt;/p&gt;
&lt;p&gt;`_maybe_update_replicated_unlocked` never checks `t_invalid`, so a claim that a signed contradiction verdict has marked invalid can still climb to REPLICATED through convergence detection, and it pulls an honest peer up with it.&lt;/p&gt;
&lt;p&gt;Three gaps line up:&lt;/p&gt;
&lt;p&gt;- The new-claim short-circuit reads only `status` and `asserter_keyid` (`core.py:1339-1352`); an invalidated but still-`open` new claim passes.
- The candidate-peer SELECT filters `status = &amp;#39;open&amp;#39;`, `unresolved = 0`, and `transparency_logged = 1` but has no `t_invalid` predicate (`core.py:1390-1410`), so an invalidated existing claim qualifies as a convergence partner.
- The promotion UPDATE gates only on `status = &amp;#39;open&amp;#39;` (`core.py:1422-1426`), leaving a TOCTOU window even after the SELECT is fixed.&lt;/p&gt;
&lt;p&gt;A signed contradiction verdict is meant to be terminal for the trust ladder: `validate_claim` refuses to promote a `t_invalid` claim to ESTABLISHED, and `record_replication_verdict` already gates its promotion UPDATE on `t_invalid IS NULL`. Convergence promotion is the one path that ignores the verdict. Reproduced at runtime: contradict claim X (t_invalid set, still PRELIMINARY), then assert peer Y sharing X&amp;#39;s ESTABLISHED anchor; both X and Y land at REPLICATED, with X&amp;#39;s `t_invalid` still set.&lt;/p&gt;
&lt;p&gt;## Severity and impact&lt;/p&gt;
&lt;p&gt;**High.** A refuted claim re-enters the trust ladder at REPLICATED after its contradiction, and it serves as the corroborating peer that promotes an honest claim. Both outcomes contradict the document…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: mareforma&lt;/p&gt;
&lt;p&gt;## What&amp;#39;s wrong&lt;/p&gt;
&lt;p&gt;`_maybe_update_replicated_unlocked` never checks `t_invalid`, so a claim that a signed contradiction verdict has marked invalid can still climb to REPLICATED through convergence detection, and it pulls an honest peer up with it.&lt;/p&gt;
&lt;p&gt;Three gaps line up:&lt;/p&gt;
&lt;p&gt;- The new-claim short-circuit reads only `status` and `asserter_keyid` (`core.py:1339-1352`); an invalidated but still-`open` new claim passes.
- The candidate-peer SELECT filters `status = &amp;#39;open&amp;#39;`, `unresolved = 0`, and `transparency_logged = 1` but has no `t_invalid` predicate (`core.py:1390-1410`), so an invalidated existing claim qualifies as a convergence partner.
- The promotion UPDATE gates only on `status = &amp;#39;open&amp;#39;` (`core.py:1422-1426`), leaving a TOCTOU window even after the SELECT is fixed.&lt;/p&gt;
&lt;p&gt;A signed contradiction verdict is meant to be terminal for the trust ladder: `validate_claim` refuses to promote a `t_invalid` claim to ESTABLISHED, and `record_replication_verdict` already gates its promotion UPDATE on `t_invalid IS NULL`. Convergence promotion is the one path that ignores the verdict. Reproduced at runtime: contradict claim X (t_invalid set, still PRELIMINARY), then assert peer Y sharing X&amp;#39;s ESTABLISHED anchor; both X and Y land at REPLICATED, with X&amp;#39;s `t_invalid` still set.&lt;/p&gt;
&lt;p&gt;## Severity and impact&lt;/p&gt;
&lt;p&gt;**High.** A refuted claim re-enters the trust ladder at REPLICATED after its contradiction, and it serves as the corroborating peer that promotes an honest claim. Both outcomes contradict the document…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rgg9-956j-3378</guid>
    </item>
  </channel>
</rss>
