Skip to main content
VulnerabilityPublished

CVE-2026-71534: Mareforma · transparency_logged trusts the unsigned rekor block

Affects mareformaSource GCVE Database

0
Compare
Authoritative record:CVE-2026-71534· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium : upgrade to 0.3.8 when convenient.

Data as of 19 Nov 2026, 17:21 UTC

CVSS 4.0 base score
6.9Medium
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.06.9
Patch
Available – fixed in 0.3.8
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/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 fixes this issue by requiring cryptographic verification of Rekor inclusion before setting transparency_logged to 1 and restoring the original write-time value when Rekor is not used. Users should upgrade to version 0.3.8 or later to remediate this vulnerability.

Description

CVE-2026-71534 is a vulnerability in mareforma versions >=0.3.0 and <0.3.8 where the transparency_logged flag is incorrectly derived from an unsigned Rekor metadata block. This allows an attacker who can edit claims.toml to forge the Rekor-witnessed state without actual logging. Additionally, honest configurations without Rekor suffer silent trust degradation after restore operations, preventing convergence to the REPLICATED state. The issue is fixed in version 0.3.8.

References

Community reviews

Loading reviews…