CVE-2026-77331

memtomem-stm recovery races could reuse a cancelled session

memtomem · memtomem-stm

First documented disclosure · Review checkpoint

Summary

Concurrent memory-service failures could corrupt recovery state or degrade the local service.

Severity and exploitation evidence

Low · 2.0/10 · CVSS 4.0. Severity source.

Exploitation not established: Public evidence describes a weakness, source correction or controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Multiple reconnects can own one dirty session, and cancellation can leave replacement transport reusable.

Conditions required

Local low-privilege influence over concurrent surfacing RPC failures or cancellation timing.

Potential impact

Session-state integrity loss and local availability degradation.

Affected versions and configurations

0.1.2–0.1.33; duplicate-reconnect subcase begins at 0.1.24.

Fix and mitigation status

0.1.34.

Practical next steps

Upgrade to 0.1.34 or later.

Operating lesson

Bind reconnect ownership and cancellation to a monotonic session generation.

Evidence and limits

The correction uses one shielded reconnect flight per dirty generation. CNA publication 2026-11-20 is distinct from the earliest reviewed public source. GitHub_M assessment: CVSS 4.0 2.

Sources