CVE-2026-77332: memtomem-stm · Surfaced memory data can escape the Markdown compatibility boundary
Affects memtomem-stmSource GCVE Database
Not known to be exploited · CVSS 2.3 Low : upgrade to 0.1.34 when convenient.
Data as of 21 Nov 2026, 00:32 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 2.3 |
|---|
- Patch
- Available – fixed in 0.1.34
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| PyPImemtomem-stm | Affected
| Fixed in
|
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 vulnerability by properly serializing untrusted fields and validating memory identifiers. Users should upgrade to version 0.1.34 or later to remediate this issue. No additional mitigation actions are required as the fix fully addresses the vulnerability.
Description
CVE-2026-77332 is a low-severity vulnerability in memtomem-stm versions from 0.1.0 up to but not including 0.1.34. It involves untrusted long-term and working-memory fields that can introduce Markdown or HTML-compatible structures into the surfaced-memory envelope, potentially misleading structural boundaries or visually concealing content. The issue is addressed in version 0.1.34 by serializing untrusted fields as inert single-line data, validating memory identifiers, and adding an explicit untrusted-data preamble. The vulnerability does not involve remote code execution or privilege escalation and has no known exploits in the wild.
References
- github.com/memtomem/memtomem-stm/security/advisories/GHSA-43hx-xm7w-3mhj (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-77332 (opens in a new tab)
- github.com/memtomem/memtomem-stm/commit/3d50ba61cbfafba6db261e35c18eed0c3805b390 (opens in a new tab)
- github.com/memtomem/memtomem-stm (opens in a new tab)
- github.com/memtomem/memtomem-stm/releases/tag/v0.1.34 (opens in a new tab)