CVE-2026-77331
memtomem-stm: Concurrent LTM recovery can duplicate reconnects or reuse a cancelled transport session
Impact
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.
An attacker can exploit this with local access to the system, with a regular user account, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: low risk of data or systems being changed, low risk of outages.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| pip | memtomem-stm | >= 0.1.2, <= 0.1.33 | 0.1.34 |
Affected products · Memtomem
| Product | Affected versions |
|---|---|
| Memtomem-stm | from 0.1.2, before 0.1.34 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- 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
- https://github.com/advisories/GHSA-72jh-722p-rqr3
- https://nvd.nist.gov/vuln/detail/CVE-2026-77331