memtomem-stm race condition in LTM recovery enables session reuse
- Exploited
- No known exploitation
- Fix
- Fixed in 0.1.34
- Who is exposed
- Not reported
Summary
memtomem-stm, a short-term memory proxy gateway for AI agents, mishandles concurrent memory-recovery reconnects and cancelled requests. A local attacker with low-privilege login and no user action needed can cause duplicate reconnects or reuse a cancelled transport session, leading to lost session-state integrity or degraded local service.
Written by a model
Original description
memtomem-stm is a short-term memory proxy gateway with proactive memory surfacing for AI agents. From 0.1.2 until 0.1.34, concurrent surfacing RPC failures can start more than one reconnect for the same dirty session because concurrent LTM recovery is not uniquely owned by a session generation. Cancellation during a post-reconnect retry can also leave the replacement transport reusable after an interrupted protocol exchange, causing session-state integrity loss or local service degradation. The duplicate-reconnect subcase was introduced in 0.1.24, while the cancellation-recovery subcase affects the broader listed range. This issue is fixed in version 0.1.34.
What to do
Upgrade to a fixed version: 0.1.34.
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-77331 (memtomem-stm: Concurrent LTM recovery can duplicate reconnects or reuse a cancelled transport session), 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-77331 (entry last updated 2026-11-20):
Affected:
- memtomem memtomem-stm: from 0.1.2, fixed in 0.1.34
Fixed versions: 0.1.34.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-77331 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77331 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/memtomem/memtomem-stm/security/advisories/GHSA-72jh-722p-rqr3
- https://github.com/memtomem/memtomem-stm/commit/761db1802df7ce4881ff4c3acee6d674925da498
- https://github.com/memtomem/memtomem-stm/releases/tag/v0.1.34
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-77331
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-77331"}.Affected versions
- memtomem memtomem-stmFrom 0.1.2 · fixed in 0.1.34
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity2/10CVSS 2.0
- No patch0/5No signal
What would change the score
- Would score about 57 if added to CISA KEV
- Would score about 52 if CISA's SSVC rates exploitation active
- Would score about 24 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · memtomem/memtomem-stm · Advisory GHSA-72jh-722p-rqr3 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-77331 |
| Record | NVD · CVE-2026-77331 |
| Other links 2 | |
| Repository | GitHub · memtomem/memtomem-stm · Commit 761db180 |
| Repository | GitHub · memtomem/memtomem-stm · Release v0.1.34 |
Questions about CVE-2026-77331
Is CVE-2026-77331 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-77331?
memtomem-stm: from 0.1.2 before 0.1.34.
Source: cve.now feed data
How do I fix CVE-2026-77331?
Upgrade to a fixed version: 0.1.34.
Source: cve.now feed data
Related
- CVE-2026-77332memtomem-stm: Surfaced memory data can escape the Markdown compatibility boundary
- CVE-2026-126280NocoDB before 2026.08.0 Refresh Token Reuse via Non-Atomic Rotation
- CVE-2026-125423Gitea command execution through repository auto-initialization
- CVE-2026-126278NocoDB before 2026.08.1 Password Reset Token Race Condition
- CVE-2026-130179Credential Overwriting in Okta .NET SDK Abstractions Library
- CVE-2026-126088Concurrent Execution using Shared Resource with Improper Synchronization in Autonomy Logic OpenPLC Runtime
No corrections so far. Something wrong on this page? Report an error.