<?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 21:58:05 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-409064</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-409064</link>
      <description>EUVD-2026-409064</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-409064</guid>
    </item>
    <item>
      <title>fkie_cve-2026-71533</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-71533</link>
      <description>&lt;p&gt;Mareforma is a local verification layer for AI-assisted research. From 0.3.7 until 0.3.8, search_claims in mareforma/db/core.py does not call _row_verified_on_read and therefore does not provide the same high-trust verification projection as query_claims. A forged or tampered REPLICATED or ESTABLISHED row that query_claims excludes can be returned by search_claims at its persisted trust level, and the missing verified marker prevents consumers from detecting that signature verification was skipped. The include_unverified option does not authorize this high-trust bypass. 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.7 until 0.3.8, search_claims in mareforma/db/core.py does not call _row_verified_on_read and therefore does not provide the same high-trust verification projection as query_claims. A forged or tampered REPLICATED or ESTABLISHED row that query_claims excludes can be returned by search_claims at its persisted trust level, and the missing verified marker prevents consumers from detecting that signature verification was skipped. The include_unverified option does not authorize this high-trust bypass. 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-71533</guid>
    </item>
    <item>
      <title>GHSA-m29v-3g7g-9c63 — Mareforma: search_claims skips verify-on-read, serving forged rows</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m29v-3g7g-9c63</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;`search_claims` never calls `_row_verified_on_read`. Its row loop applies only the PRELIMINARY-unenrolled filter, then appends the row. `query_claims` runs the same projection but additionally re-verifies REPLICATED/ESTABLISHED signatures on read (line 4023) and drops any row that fails, per the documented tamper guarantee in the comment block above it: a high-trust row whose signature does not verify is excluded from query results entirely.&lt;/p&gt;
&lt;p&gt;So a tampered or forged high-trust row splits the two read paths. Any process with DB write access, or an attacker copying a genuine validation envelope onto a fresh row, can flip a row to ESTABLISHED. `query()` drops it; `search()` serves it at its persisted trust level. Verified in a runtime check against a forged ESTABLISHED row:&lt;/p&gt;
&lt;p&gt;```
query() returns forged row: False
search() returns forged row: True   # support_level ESTABLISHED, &amp;#39;verified&amp;#39; key absent
```&lt;/p&gt;
&lt;p&gt;The docstring makes this worse: `search_claims` promises &amp;#34;the same projection as query_claims&amp;#34; and that the `include_unverified` filter &amp;#34;applies identically&amp;#34;, so callers reasonably trust search results equally. The forged row also lacks the `verified` key entirely, so a consumer cannot tell it went unchecked.&lt;/p&gt;
&lt;p&gt;## Severity and impact&lt;/p&gt;
&lt;p&gt;**High.** The verify-on-read tamper exclusion is a stated trust guarantee, and search is a primary read surface. A forged ESTABLISHED finding that query correctly rejects is served by search as genuine, with no marker that verificati…&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;`search_claims` never calls `_row_verified_on_read`. Its row loop applies only the PRELIMINARY-unenrolled filter, then appends the row. `query_claims` runs the same projection but additionally re-verifies REPLICATED/ESTABLISHED signatures on read (line 4023) and drops any row that fails, per the documented tamper guarantee in the comment block above it: a high-trust row whose signature does not verify is excluded from query results entirely.&lt;/p&gt;
&lt;p&gt;So a tampered or forged high-trust row splits the two read paths. Any process with DB write access, or an attacker copying a genuine validation envelope onto a fresh row, can flip a row to ESTABLISHED. `query()` drops it; `search()` serves it at its persisted trust level. Verified in a runtime check against a forged ESTABLISHED row:&lt;/p&gt;
&lt;p&gt;```
query() returns forged row: False
search() returns forged row: True   # support_level ESTABLISHED, &amp;#39;verified&amp;#39; key absent
```&lt;/p&gt;
&lt;p&gt;The docstring makes this worse: `search_claims` promises &amp;#34;the same projection as query_claims&amp;#34; and that the `include_unverified` filter &amp;#34;applies identically&amp;#34;, so callers reasonably trust search results equally. The forged row also lacks the `verified` key entirely, so a consumer cannot tell it went unchecked.&lt;/p&gt;
&lt;p&gt;## Severity and impact&lt;/p&gt;
&lt;p&gt;**High.** The verify-on-read tamper exclusion is a stated trust guarantee, and search is a primary read surface. A forged ESTABLISHED finding that query correctly rejects is served by search as genuine, with no marker that verificati…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m29v-3g7g-9c63</guid>
    </item>
  </channel>
</rss>
