Skip to main content
Menu
CVEs

CVE

Mareforma signature bypass in transparency_logged restore

CVE-2026-71534Published Updated Summary written by a model

6.9MediumCNA
Exploited
No known exploitation
Fix
Fixed in 0.3.8
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.3.8.

Summary

Mareforma, a local verification layer for AI-assisted research, trusts an unsigned transparency-log field during restore. A local attacker with low privileges who edits claims.toml can falsely make a claim eligible for REPLICATED convergence, and no user action is needed. The same flaw can also reset signed claims in non-Rekor graphs, permanently blocking their convergence.

Original description

Mareforma is a local verification layer for AI-assisted research. From 0.3.0 until 0.3.8, restore logic in mareforma/db/restore.py derives transparency_logged from the unsigned rekor.uuid field inside signature_bundle without requiring a verified claim-bound rekor_inclusions entry, so an attacker who modifies claims.toml can falsely make a claim eligible for REPLICATED convergence. The same logic resets signed claims in non-Rekor graphs from transparency_logged 1 to 0 after restore, permanently preventing convergence because no Rekor refresh is configured. This issue is fixed in version 0.3.8.

cve.now Index

7Pcve.now Index 7 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • 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 29 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 0.3.8.

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-71534 (Mareforma: transparency_logged trusts the unsigned rekor block), 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-71534 (entry last updated 2026-11-18):
Affected:
- mareforma mareforma: from 0.3.0, fixed in 0.3.8
Fixed versions: 0.3.8.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-71534 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-71534 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-xfq4-8hf9-5h43
- https://github.com/mareforma/mareforma/pull/58
- https://github.com/mareforma/mareforma/commit/cccbf4eafd3c34b20b1686f12c0cad76c87566ae
- https://github.com/mareforma/mareforma/releases/tag/v0.3.8
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-71534
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-71534"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • mareforma mareforma

    From 0.3.0 · fixed in 0.3.8

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · mareforma/mareforma · Advisory GHSA-xfq4-8hf9-5h43
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-71534
RecordNVD · CVE-2026-71534
Other links 3
RepositoryGitHub · mareforma/mareforma · Pull request #58
RepositoryGitHub · mareforma/mareforma · Commit cccbf4ea
RepositoryGitHub · mareforma/mareforma · Release v0.3.8

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-71534

Is CVE-2026-71534 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

Which versions are affected by CVE-2026-71534?

mareforma: from 0.3.0 before 0.3.8.Source: cve.now feed data

How do I fix CVE-2026-71534?

Upgrade to a fixed version: 0.3.8.Source: cve.now feed data

More CVEs