memtomem-stm: Concurrent LTM recovery can duplicate reconnects or reuse a cancelled transport session
GHSA-72jh-722p-rqr3 · CVE-2026-77331
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
Concurrent surfacing RPC failures can trigger more than one reconnect for the same dirty session, and cancellation during a post-reconnect retry can leave the replacement session reusable despite an interrupted protocol exchange. The private fix introduces monotonic session generations, one shielded shared reconnect flight per dirty generation, and generation-aware cancellation handling across search, access-count, and scratch RPCs. The duplicate-reconnect subcase was introduced in 0.1.24; cancellation recovery affects the broader listed range.
References
- WEB https://github.com/memtomem/memtomem-stm/security/advisories/GHSA-72jh-722p-rqr3
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-77331
- WEB https://github.com/memtomem/memtomem-stm/commit/761db1802df7ce4881ff4c3acee6d674925da498
- PACKAGE https://github.com/memtomem/memtomem-stm
- WEB https://github.com/memtomem/memtomem-stm/releases/tag/v0.1.34
Ready to move
Start Securing
Free, no credit card | First findings in minutes