CVE-2026-71535: Mareforma: Unsigned Claims Can Be Promoted to REPLICATED via Missing Signature Enforcement in Convergence Path
Mareforma is a local verification layer for AI-assisted research. From 0.3.0 until 0.3.7, the maybeupdatereplicatedunlocked convergence path in mareforma/db/core.py uses generatedby labels without requiring a valid signaturebundle from a distinct enrolled signer, so an unsigned claim written to a shared graph can converge with a signed peer and be promoted to REPLICATED. The forged trust state is returned by queries requiring REPLICATED support, allowing false multi-party endorsement signals to reach downstream consumers. This issue is fixed in version 0.3.7.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 0.3.7
Event History
Frequently Asked Questions
Which deployments are exposed to false REPLICATED trust states?
Deployments using Mareforma versions from 0.3.0 until the 0.3.7 fix are affected when claims are written to a shared graph and downstream consumers rely on queries requiring REPLICATED support.
What does an attacker need to do to trigger the issue?
An attacker needs to get an unsigned claim written into a shared graph with generated_by labels. During convergence with a signed peer, the vulnerable path can promote that claim to REPLICATED without requiring a valid signature bundle from a distinct enrolled signer.
What is the practical impact of successful exploitation?
Queries that require REPLICATED support can return the forged trust state. Downstream consumers may therefore treat a claim as having multi-party endorsement when it does not.
What remediation is identified?
Update Mareforma to version 0.3.7, which fixes the issue.