Skip to main content
VulnerabilityPublished

CVE-2026-71534: mareforma · Insufficient Verification of Data Authenticity

Affects mareformaSource CVE Database V5

0
Compare

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

Data as of 18 Nov 2026, 23:04 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
mareformamareformaAffected
  • >=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

Upgrade mareforma to version 0.3.8 or later, where this vulnerability is fixed. No other mitigation is required as the fix addresses the root cause by properly verifying claim-bound rekor_inclusions entries before deriving transparency_logged.

Description

CVE-2026-71534 is a vulnerability in mareforma versions 0.3.0 through 0.3.7 where the restore logic improperly derives the transparency_logged flag from an unsigned field without verifying claim-bound entries. This allows an attacker to manipulate claims.toml to falsely mark claims as eligible for REPLICATED convergence. Additionally, in non-Rekor graphs, the logic resets signed claims from transparency_logged 1 to 0 after restore, preventing convergence permanently. The issue is fixed in version 0.3.8.

References

Community reviews

Loading reviews…