Skip to main content
Menu
CVEs

CVE

Mareforma signature verification bypass in search_claims

CVE-2026-71533Published Updated Summary written by a model

6.8MediumCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Summary

Mareforma, a local verification layer for AI-assisted research, has a flaw in its search_claims function that skips the verification step used by query_claims. A local attacker with low privileges and no required user action can get forged or tampered REPLICATED or ESTABLISHED claim records returned by search, where they appear at their stored trust level without any marker showing that verification was skipped.

Original description

Mareforma is a local verification layer for AI-assisted research. From 0.3.7 until 0.3.8, search_claims in mareforma/db/core.py does not call _row_verified_on_read and therefore does not provide the same high-trust verification projection as query_claims. A forged or tampered REPLICATED or ESTABLISHED row that query_claims excludes can be returned by search_claims at its persisted trust level, and the missing verified marker prevents consumers from detecting that signature verification was skipped. The include_unverified option does not authorize this high-trust bypass. This issue is fixed in version 0.3.8.

cve.now Index

12Pcve.now Index 12 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.8/10CVSS 6.8
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-71533 (Mareforma: search_claims skips verify-on-read, serving forged rows), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-71533 (entry last updated 2026-11-18):
Affected:
- mareforma mareforma: versions 0.3.7
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-71533 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-71533 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/mareforma/mareforma/security/advisories/GHSA-m29v-3g7g-9c63
- https://github.com/mareforma/mareforma/pull/58
- https://github.com/mareforma/mareforma/commit/8b5291792128326a22f240123659d2754446c194
- https://github.com/mareforma/mareforma/releases/tag/v0.3.8
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-71533
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-71533"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • mareforma mareforma

    0.3.7

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · mareforma/mareforma · Advisory GHSA-m29v-3g7g-9c63
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-71533
RecordNVD · CVE-2026-71533
Other links 3
RepositoryGitHub · mareforma/mareforma · Pull request #58
RepositoryGitHub · mareforma/mareforma · Commit 8b529179
RepositoryGitHub · mareforma/mareforma · Release v0.3.8

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-71533

Is CVE-2026-71533 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-71533?

mareforma: version 0.3.7.Source: cve.now feed data

More CVEs