Medium

Mareforma: search_claims skips verify-on-read, serving forged rows

  • Disclosed: 19.11.2026
  • Updated: 19.11.2026 18:17

What's wrong

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.

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:

query() returns forged row: False
search() returns forged row: True   # support_level ESTABLISHED, 'verified' key absent

The docstring makes this worse: search_claims promises "the same projection as query_claims" and that the include_unverified filter "applies identically", so callers reasonably trust search results equally. The forged row also lacks the verified key entirely, so a consumer cannot tell it went unchecked.

Severity and impact

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 verification was skipped.

Location

  • mareforma/db/core.py:4206 search_claims row loop applies only the PRELIMINARY-unenrolled filter, then appends
  • mareforma/db/core.py:4114 search_claims signature and docstring, which claims query_claims-identical semantics
  • mareforma/db/core.py:4023 query_claims verify-on-read call that search_claims lacks

Fix direction

Mirror query_claims: add a verify_cache: dict = {} and, inside the search_claims row loop after the include_unverified check, drop rows that fail _row_verified_on_read(conn, d, verify_cache). Since the verify filter can drop rows even when include_unverified=True, remove the single-batch break on include_unverified and keep batching until limit survivors or the FTS5 match-set is exhausted, with the same scan ceiling query_claims uses. Also set single_trust_domain / trust_domain_root on surviving ESTABLISHED rows if the "same projection" promise is to hold.

Do red/green TDD: add a regression test that fails on main, then make it pass.

Quality bar

SOLID, DRY, KISS. Clean, readable, well-tested code. No new errors, warnings, or test failures; the full suite stays green on all supported Python versions.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) mareforma >= 0.3.7, < 0.3.8 0.3.8

References

CVSS score -
CVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Weakness (CWE)
CWE-347
Platform
Python (PyPI)
Package
mareforma
Disclosed
19.11.2026
Updated
19.11.2026 18:17

Sources and licenses

OSV / GitHub Advisory Database - GHSA-m29v-3g7g-9c63 - CC BY 4.0

Vulnerability history: mareforma

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

Total entries
5
First → latest
11.2026 11.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 2
  • Medium 3

Disclosures per year

  1. 2026: 5
  1. Medium CVE-2026-71534 >= 0.3.0, < 0.3.8 0.3.8
  2. Medium CVE-2026-71500 >= 0.3.0, < 0.3.8 0.3.8
  3. High CVE-2026-71536 >= 0.3.0, < 0.3.8 0.3.8
  4. Mareforma: search_claims skips verify-on-read, serving forged rows this entry
    Medium CVE-2026-71533 >= 0.3.7, < 0.3.8 0.3.8

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.