Skip to main content
VulnerabilityPublished

CVE-2026-71536: Mareforma · verify_bundle never checks a per-claim signature

Affects mareformaSource GCVE Database

0
Compare
Authoritative record:CVE-2026-71536· High 7.0

Not known to be exploited · CVSS 7.0 High : upgrade to 0.3.8 soon.

Data as of 19 Nov 2026, 17:20 UTC

CVSS 4.0 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.07.0
Patch
Available – fixed in 0.3.8
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade mareforma to 0.3.8.

Affected software

ProductAffectedFixed in
PyPImareformaAffected
  • >=0.3.0 <0.3.8
Fixed in
  • 0.3.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in mareforma version 0.3.8 that addresses this issue. Users should upgrade to version 0.3.8 or later. Until upgrading, users should be aware that verify_bundle does not verify per-claim signatures despite documentation claims. The vendor recommends either implementing cryptographic verification of each claim's signature or correcting the documentation to reflect the actual verification scope. No additional mitigations are indicated beyond applying the official fix.

Description

The mareforma package's verify_bundle function claims to verify each per-claim signature within a DSSE bundle but does not actually perform cryptographic verification of individual claim signatures. Instead, it only checks internal digest consistency, allowing a malicious or compromised exporter key holder to produce bundles with missing, invalid, or forged claim signatures that still pass verification. This undermines the trust boundary the export mechanism is intended to provide. A fix is available in version 0.3.8.

References

Community reviews

Loading reviews…