CVE-2026-71533: Mareforma · search_claims skips verify-on-read, serving forged rows
Affects mareformaSource GCVE Database
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
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 6.8 |
|---|
- 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:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| PyPImareforma | Affected
| Fixed in
|
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 vulnerability by adding verify-on-read checks to search_claims, aligning its behavior with query_claims. Users should upgrade to version 0.3.8 or later. The fix includes adding a verification cache, dropping rows that fail verification, adjusting batching logic to continue scanning until the limit of verified rows is reached, and setting trust domain attributes on surviving rows. Applying this official fix fully mitigates the issue.
Description
The Mareforma package contains a vulnerability in the search_claims function where it skips the verify-on-read step, allowing forged or tampered rows with high trust levels to be served without verification. This results in search_claims returning forged ESTABLISHED rows that query_claims correctly excludes, violating the documented tamper guarantee. The flaw arises because search_claims applies only a preliminary filter and does not re-verify signatures on read, unlike query_claims. A fix is available in version 0.3.8 that aligns search_claims behavior with query_claims by adding verification and adjusting batching logic.
References
- github.com/mareforma/mareforma/security/advisories/GHSA-m29v-3g7g-9c63 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-71533 (opens in a new tab)
- github.com/mareforma/mareforma/pull/58 (opens in a new tab)
- github.com/mareforma/mareforma/commit/8b5291792128326a22f240123659d2754446c194 (opens in a new tab)
- github.com/mareforma/mareforma (opens in a new tab)
- github.com/mareforma/mareforma/releases/tag/v0.3.8 (opens in a new tab)