Skip to main content

CVE-2026-71535mareforma improper signature verification

Schedule itHigh7.1EPSS not scored yet

CVE-2026-71535 is a improper signature verification in mareforma, rated high (7.1 on CVSS 3.1).

Why this priority: High severity, with no exploitation signal yet.

Published · Updated · NVD status: Received

What it is

A cryptographic signature is not checked properly, so forged data is accepted.

How it is reached

An attacker can exploit it by someone who can already run code or sign in on the machine, without an account, and nobody has to click anything.

What an attacker gains

A successful attack can change data or behaviour. In practice, this kind of flaw lets an attacker read or tamper with traffic, or pass a forged message as genuine. The damage can spread past the vulnerable component into others.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade mareforma to 0.3.7 or later.
  2. Limit who can run code or sign in on the hosts that run it.

Description from NVD

Mareforma is a local verification layer for AI-assisted research. From 0.3.0 until 0.3.7, the _maybe_update_replicated_unlocked convergence path in mareforma/db/core.py uses generated_by labels without requiring a valid signature_bundle from a distinct enrolled signer, so an unsigned claim written to a shared graph can converge with a signed peer and be promoted to REPLICATED. The forged trust state is returned by queries requiring REPLICATED support, allowing false multi-party endorsement signals to reach downstream consumers. This issue is fixed in version 0.3.7.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • TLS termination and service-to-service channels. The flaw sits on the network path between clients and services.
  • Signature checks. The flaw sits on the network path between clients and services.

Trust boundaries in play

  • Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
  • Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
  • On the network path between clients and services. An attacker who crosses it can read or tamper with traffic, or pass a forged message as genuine.

Questions to answer about your own systems

  • Where does mareforma run in your systems, and at which version?
  • Which of those hosts also run code or users you do not fully trust?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.