Skip to content
Threat Brief

← All advisories

CVE-2026-77331

Low 2.0No known exploitationFix available

memtomem-stm: Concurrent LTM recovery can duplicate reconnects or reuse a cancelled transport session

Vendor advisory: GHSA-72jh-722p-rqr3

Record last updated

CVSS score

2.0

Low on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

None

No EPSS score available

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-362

Patching and mitigation

Patch status
Fix available (source: GitHub Advisory Database)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
pipmemtomem-stmfrom 0.1.2 up to and including 0.1.330.1.34GitHub Advisory Database

Timeline

  1. Patch

    Fix documented by GitHub Advisory Database

    Source: GitHub Advisory Database (opens in a new tab)

Vendor guidance and references