CVE-2026-77331

GHSA-72jh-722p-rqr3 · published 20 Nov 2026 · updated 20 Nov 2026

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

2.0LowCVSS 2.0EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in memtomem-stm 0.1.34.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
memtomem>=0.1.2 <0.1.34
pypi: memtomem-stm>=0.1.2 <0.1.34, >=0.1.2 <=0.1.330.1.34

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in memtomem-stm (PyPI), strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-77331 severity on Zeptric[![CVE-2026-77331](https://zeptric.io/badge/cve/CVE-2026-77331.svg)](https://zeptric.io/cve/CVE-2026-77331)