Skip to main content
Menu
CVEs

CVE

Mareforma signature verification bypass in verify_bundle

Affects mareforma 0.3.0 up to but not including 0.3.8, where verify_bundle does not check per-claim asserter signatures. No vendor severity is given; CVSS rates it 7 (high). The listed fixed version is 0.3.8.

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

7.0HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.3.8
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.8. Consumers rely on verify_bundle to check export bundles for per-claim authenticity.

Summary

Mareforma's verify_bundle check does not verify the individual signature on each claim, so claims with missing, invalid, or forged asserter signatures can be accepted as authentic. An attacker can reach this remotely without logging in, but a user must take an action for the attack to work.

Original description

Mareforma is a local verification layer for AI-assisted research. From 0.3.0 until 0.3.8, verify_bundle in mareforma/export_bundle.py validates the outer DSSE envelope and exporter-signed subject digests, but JSONLDExporter._claim_node in mareforma/exporters/jsonld.py supplies no signatureBundle for individual claims. Because the exporter signs both the predicate nodes and their digest list, the check proves only internal bundle consistency and allows claims with missing, invalid, or forged asserter signatures to be accepted as authentic. This issue is fixed in version 0.3.8.

Who should check

Teams running mareforma 0.3.x (0.3.0 before 0.3.8) that produce or verify export bundles with verify_bundle and rely on them for per-claim authenticity.

“>= 0.3.0, < 0.3.8”

github.com

cve.now Index

19Pcve.now Index 19 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7/10CVSS 7.0
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active

What to do

  • Check whether your setup matches what the bug needs.

    Mareforma versions 0.3.0 up to but not including 0.3.8. Consumers rely on verify_bundle to check export bundles for per-claim authenticity.
  • 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-71536 (Mareforma: verify_bundle never checks a per-claim signature), 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-71536 (entry last updated 2026-11-18):
Affected:
- mareforma mareforma: from 0.3.0, fixed in 0.3.8
Fixed versions: 0.3.8.
Conditions (all must be true for the bug to be hit):
- Mareforma versions 0.3.0 up to but not including 0.3.8. (source: https://github.com/mareforma/mareforma/security/advisories/GHSA-hxh5-gp44-rc6p)
- Consumers rely on verify_bundle to check export bundles for per-claim authenticity. (source: https://github.com/mareforma/mareforma/security/advisories/GHSA-hxh5-gp44-rc6p)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-71536 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-71536 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-hxh5-gp44-rc6p
- https://github.com/mareforma/mareforma/pull/58
- https://github.com/mareforma/mareforma/commit/20caa4a5a9557a140a09a5d2c1c4a6a2124c0cc3
- 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-71536
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-71536"}.

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-hxh5-gp44-rc6p
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-71536
RecordNVD · CVE-2026-71536
Other links 3
RepositoryGitHub · mareforma/mareforma · Pull request #58
RepositoryGitHub · mareforma/mareforma · Commit 20caa4a5
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-71536

Is CVE-2026-71536 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?

verify_bundle, which consumers rely on to check export bundles for per-claim authenticity, can report success for a bundle whose claims have missing, invalid, or forged asserter signatures. Those claims are then accepted as authentic. The impact is described for someone holding the exporter key or a malicious exporter.Source: github.com

Which versions are affected by CVE-2026-71536?

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

Am I affected, and how do I check?

Mareforma versions from 0.3.0 up to but not including 0.3.8 are in the affected range. To check an installed version, look at the mareforma package version in the environment where verify_bundle runs.Source: github.com

How do I fix CVE-2026-71536?

The listed fixed version is 0.3.8, so move to 0.3.8 or later. The sources give no separate fix record or patch identifiers for this issue.Source: github.com

More CVEs