High

Mareforma: verify_bundle never checks a per-claim signature

  • Disclosed: 19.11.2026
  • Updated: 20.11.2026 10:00

Summary

verify_bundle documents that it verifies "a bundle's DSSE envelope AND each per-claim signature", lists "per-claim signature failure" among its raised errors, and promises that partial verification never surfaces "an authenticated bundle that contains some invalid claims" as success. In practice, the code does not do this.

The JSON-LD predicate built by JSONLDExporter._claim_node carries no signature material (there is no signatureBundle field on the node), leaving the verification loop without cryptographic data to check per claim. It only re-derives each claim's canonical-statement digest from the node fields and compares it to the signed subject list:

python
chain_input = _signing.canonical_statement({...node fields...}, node.get("evidence") or {})
expected = hashlib.sha256(chain_input).hexdigest()
if subjects[subject_name] != expected:
    raise BundleVerificationError(...)

This digest check is self-referential: the exporter signs both the subject digests and the predicate nodes using the same key. It confirms internal consistency as built, but does not verify that a claim's purported asserter ever validly signed it. The test test_tampered_claim_text_in_predicate_fails asserts a "digest mismatch", reflecting that digest-only verification is the actual behavior.

Severity and impact

All trust in a bundle collapses to the single exporter key. A malicious exporter or an entity holding this key can emit a bundle containing claims with missing, invalid, or forged asserter signatures, and verify_bundle will still return success. Relying parties following the docstrings may falsely assume that per-claim authenticity was verified.

Affected locations

  • mareforma/export_bundle.py:20 module docstring claims verification checks "every per-claim signature inside predicate".
  • mareforma/export_bundle.py:183 verify_bundle docstring promises per-claim signature verification and a per-claim signature failure error.
  • mareforma/export_bundle.py:254 verify loop only recomputes and compares canonical-statement digests.
  • mareforma/exporters/jsonld.py:178 _claim_node emits no signature field, so the predicate carries nothing to verify per claim.

Fix direction

The advisory identifies two potential solutions:

  1. Export each claim's signature bundle in the JSON-LD predicate and have verify_bundle cryptographically verify it (including claim_id and subject binding) against the claim's asserter or validator key, raising on the first failure as documented.
  2. If per-claim verification is out of scope, correct the module docstring and the verify_bundle docstring to explicitly indicate that only the bundle-level DSSE signature and internal subject-digest consistency are checked, with per-claim asserter signatures omitted from validation. Add a regression test targeting main.

What to do

Upgrade to Mareforma version 0.3.8 or later.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) mareforma >= 0.3.0, < 0.3.8 0.3.8

References

CVSS score -
CVSS 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
Weakness (CWE)
CWE-347
Platform
Python (PyPI)
Package
mareforma
Disclosed
19.11.2026
Updated
20.11.2026 10:00

Sources and licenses · Edited or translated by DockRay; source rights and applicable licenses are retained.

OSV / GitHub Advisory Database - GHSA-hxh5-gp44-rc6p - CC BY 4.0

Vulnerability history: mareforma

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

Total entries
5
First → latest
11.2026 11.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • High 2
  • Medium 3

Disclosures per year

  1. 2026: 5
  1. Medium CVE-2026-71534 >= 0.3.0, < 0.3.8 0.3.8
  2. Medium CVE-2026-71500 >= 0.3.0, < 0.3.8 0.3.8
  3. Mareforma: verify_bundle never checks a per-claim signature this entry
    High CVE-2026-71536 >= 0.3.0, < 0.3.8 0.3.8
  4. Medium CVE-2026-71533 >= 0.3.7, < 0.3.8 0.3.8

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.