CVE-2026-77332: memtomem-stm · Improper Encoding or Escaping of Output
Affects memtomem-stmSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low : upgrade to 0.1.34 when convenient.
Data as of 20 Nov 2026, 17:19 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 24 Oct 2026.
What to do
Upgrade memtomem-stm to 0.1.34.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| memtomemmemtomem-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
Upgrade memtomem-stm to version 0.1.34 or later, where this vulnerability is fixed. No additional mitigation actions are required as the fix addresses the improper encoding issue.
Description
CVE-2026-77332 is a vulnerability in memtomem-stm versions 0.1.0 through 0.1.33 where untrusted long-term and working-memory fields are not properly serialized as inert data. This allows Markdown or HTML-compatible structures to be introduced into the surfaced-memory envelope, potentially misleading consuming AI agents by altering structural boundaries or visually concealing content. The issue is fixed in version 0.1.34.