Answer in brief
CVE-2026-71533 records a Medium severity (CVSS 6.8) vulnerability in Mareforma: search_claims skips verify-on-read, serving forged rows. The current sources do not mark it as known exploited. The current feed maps mareforma/mareforma (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps mareforma/mareforma (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| mareforma/mareformageneric | = 0.3.7 | Not reported |
Published upstream
Nov 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.