CVE
Mareforma unsigned claims promoted to REPLICATED in convergence path
Affects mareforma 0.3.0 up to but not including 0.3.7 on shared graphs where an attacker without a Mareforma key can write unsigned claims, with Rekor disabled (the library default). Fixed in 0.3.7.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.3.7
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Mareforma versions 0.3.0 up to but not including 0.3.7 (Affected versions >= 0.3.0, < 0.3.7). A shared graph that an attacker without a Mareforma key can write unsigned claims to. Rekor is disabled, the library default, which sets transparency_logged automatically so every claim is convergence-eligible.
Summary
Mareforma, a local verification layer for AI-assisted research, has a flaw in versions from 0.3.0 up to 0.3.7 where unsigned claims in a shared graph can be promoted to REPLICATED status without a valid signature from a distinct enrolled signer. An attacker with local access and no login can use this to make false multi-party endorsement appear in query results that downstream consumers rely on.
Original description
Mareforma is a local verification layer for AI-assisted research. From 0.3.0 until 0.3.7, the _maybe_update_replicated_unlocked convergence path in mareforma/db/core.py uses generated_by labels without requiring a valid signature_bundle 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.
Who should check
Teams running mareforma 0.3.0 through 0.3.6 with a shared graph.db that others can write to, and downstream consumers that query min_support='REPLICATED' as a multi-party endorsement signal.
“mareforma 0.3.3 contains a critical integrity flaw”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Mareforma versions 0.3.0 up to but not including 0.3.7 (Affected versions >= 0.3.0, < 0.3.7). A shared graph that an attacker without a Mareforma key can write unsigned claims to. Rekor is disabled, the library default, which sets transparency_logged automatically so every claim is convergence-eligible.Upgrade to a fixed version: 0.3.7.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-71535 (Mareforma: Unsigned Claims Can Be Promoted to REPLICATED via Missing Signature Enforcement in Convergence Path), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-71535 (entry last updated 2026-11-18):
Affected:
- mareforma mareforma: from 0.3.0, fixed in 0.3.7
Fixed versions: 0.3.7.
Conditions (all must be true for the bug to be hit):
- Mareforma versions 0.3.0 up to but not including 0.3.7 (Affected versions >= 0.3.0, < 0.3.7). (source: https://github.com/mareforma/mareforma/security/advisories/GHSA-8776-qf3h-26r3)
- A shared graph that an attacker without a Mareforma key can write unsigned claims to. (source: https://github.com/mareforma/mareforma/security/advisories/GHSA-8776-qf3h-26r3)
- Rekor is disabled, the library default, which sets transparency_logged automatically so every claim is convergence-eligible. (source: https://github.com/mareforma/mareforma/security/advisories/GHSA-8776-qf3h-26r3)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: local access, no login, no user action.
CISA KEV: CVE-2026-71535 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-71535 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/mareforma/mareforma/security/advisories/GHSA-8776-qf3h-26r3
- https://github.com/mareforma/mareforma/pull/18
- https://github.com/mareforma/mareforma/commit/e1bf09e515693a7f2a2a80852b05fa66be44302e
- https://github.com/mareforma/mareforma/releases/tag/v0.3.7
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-71535
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-71535"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- mareforma mareforma
From 0.3.0 · fixed in 0.3.7
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · mareforma/mareforma · Advisory GHSA-8776-qf3h-26r3 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-71535 |
| Record | NVD · CVE-2026-71535 |
| Other links 3 | |
| Repository | GitHub · mareforma/mareforma · Pull request #18 |
| Repository | GitHub · mareforma/mareforma · Commit e1bf09e5 |
| Repository | GitHub · mareforma/mareforma · Release v0.3.7 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-71535
Is CVE-2026-71535 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Mareforma does not require a valid signature before promoting a claim to REPLICATED in the convergence path. An attacker with no Mareforma key can write an unsigned claim to a shared graph, and it is then returned by trust queries, so downstream consumers see false multi-party endorsement.Source: github.com, github.com
Which versions are affected by CVE-2026-71535?
mareforma: from 0.3.0 before 0.3.7.Source: cve.now feed data
Am I affected, and how do I check?
Versions 0.3.0 up to but not including 0.3.7 are affected, in setups where a shared graph accepts claims from writers without a Mareforma key. Rekor is disabled by default, which makes every claim convergence-eligible. Check your installed mareforma version and whether rekor_enabled is set to False.Source: github.com, github.com
How do I fix CVE-2026-71535?
Upgrade mareforma to version 0.3.7 or later, which is the fixed version. No vendor patch identifiers are listed for this issue.Source: github.com, github.com