Skip to main content
VulnerabilityPublished

CVE-2026-71500: Mareforma · invalidated claims still promote to REPLICATED

Affects mareformaSource GCVE Database

0
Compare
Authoritative record:CVE-2026-71500· Medium 6.8

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

Data as of 19 Nov 2026, 17:21 UTC

CVSS 4.0 base score
6.8Medium
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.8
Patch
Available – fixed in 0.3.8
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/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 by adding checks for the t_invalid flag in the new-claim short-circuit, candidate-peer SELECT, and promotion UPDATE code paths, and by closing the TOCTOU window with row-level locking. Users should upgrade to version 0.3.8 or later to remediate this vulnerability. No additional mitigation steps are required beyond applying the official fix.

Description

A vulnerability in Mareforma versions 0.3.0 up to but not including 0.3.8 allows invalidated claims to be promoted to the REPLICATED status due to missing checks on the t_invalid flag during claim convergence. This flaw permits a refuted claim to re-enter the trust ladder, potentially promoting an honest claim incorrectly. The issue arises from three gaps in the code where t_invalid is not checked during new claim short-circuiting, candidate-peer selection, and promotion update, creating a time-of-check to time-of-use window. A fix is available in version 0.3.8 that properly incorporates t_invalid checks and closes the TOCTOU window.

References

Community reviews

Loading reviews…