Home/Research/Post

GHSA-hxh5-gp44-rc6p: Mareforma: verify_bundle never checks a per-claim signature

  • Severity: HIGH
  • CVE: CVE-2026-71536
  • Ecosystems: pip
  • Packages: mareforma

## What’s wrong

`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. 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), so the verify loop has nothing cryptographic 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(…)
“`

That digest check is self-referential: the exporter signs both the subject digests and the predicate nodes with the same key. It confirms the bundle is internally consistent as built, not that each claim’s purported asserter ever validly signed it. The existing test `test_tampered_claim_text_in_predicate_fails` asserts a “digest mismatch”, confirming digest-only verification is the actual contract.

## Severity and impact

**Medium.** All trust in a bundle collapses to the single exporter key. Whoever holds it (or a malicious exporter) can emit a bundle containing claims whose asserter signatures a…

Source: GitHub Security Advisories · 2026-11-19