Home/Research/Post

GHSA-rgg9-956j-3378: Mareforma: invalidated claims still promote to REPLICATED

  • Severity: MEDIUM
  • CVE: CVE-2026-71500
  • Ecosystems: pip
  • Packages: mareforma

## What’s wrong

`_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.

Three gaps line up:

– 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 = ‘open’`, `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 = ‘open’` (`core.py:1422-1426`), leaving a TOCTOU window even after the SELECT is fixed.

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’s ESTABLISHED anchor; both X and Y land at REPLICATED, with X’s `t_invalid` still set.

## Severity and impact

**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 documente…

Source: GitHub Security Advisories · 2026-11-19