Skip to main content
VulnerabilityPublished

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

Affects memtomem-stmSource GCVE Database

0
Compare
Authoritative record:CVE-2026-77331· Low 2.0

Not known to be exploited · CVSS 2.0 Low : upgrade to 0.1.34 when convenient.

Data as of 21 Nov 2026, 00:32 UTC

CVSS 4.0 base score
2.0Low
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.02.0
Patch
Available – fixed in 0.1.34
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade memtomem-stm to 0.1.34.

Affected software

ProductAffectedFixed in
PyPImemtomem-stmAffected
  • >=0.1.2 <0.1.34
Fixed in
  • 0.1.34

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in memtomem-stm version 0.1.34 that addresses this concurrency issue by introducing monotonic session generations and improved cancellation handling. Users should upgrade to version 0.1.34 or later to remediate this vulnerability.

Description

CVE-2026-77331 is a concurrency vulnerability in memtomem-stm affecting versions from 0.1.2 up to but not including 0.1.34. It involves concurrent surfacing RPC failures that can cause duplicate reconnect attempts for the same session and allow reuse of a cancelled transport session due to interrupted protocol exchanges. The issue was introduced in version 0.1.24 and affects a broader range of versions due to cancellation recovery problems. A fix is available in version 0.1.34.

References

Community reviews

Loading reviews…