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.
Metrics
Affected Vendors & Products
References
History
Sat, 21 Nov 2026 22:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Sat, 21 Nov 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Memtomem
Memtomem memtomem-stm |
|
| Vendors & Products |
Memtomem
Memtomem memtomem-stm |
Fri, 20 Nov 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | memtomem-stm: Concurrent LTM recovery can duplicate reconnects or reuse a cancelled transport session | |
| Weaknesses | CWE-362 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published: 2026-11-20T16:56:23.750Z
Updated: 2026-11-20T19:21:51.640Z
Reserved: 2026-08-20T19:24:11.618Z
Link: CVE-2026-77331
Updated: 2026-11-20T19:21:44.409Z
Status : Received
Published: 2026-11-20T17:18:27.080
Modified: 2026-11-20T20:17:47.453
Link: CVE-2026-77331
No data.