CVE-2026-77332: memtomem-stm: Surfaced memory data can escape the Markdown compatibility boundary
Low
- OSV id
- GHSA-43hx-xm7w-3mhj
- Also known as
- CVE-2026-77332
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| memtomem-stm PyPI |
>= 0.1.0, < 0.1.34 | 0.1.34 |
How to fix it
Upgrade memtomem-stm to 0.1.34 or later.
# in requirements.txt: change the line to memtomem-stm==0.1.34
pip install -r requirements.txt
- If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
Untrusted long-term and working-memory fields can introduce Markdown or HTML-compatible structure into the surfaced-memory envelope. A crafted memory may create misleading structural boundaries or visually conceal content. The private fix serializes every untrusted field as inert single-line data, validates copyable memory identifiers, and pins an explicit untrusted-data preamble. Ordinary natural-language persuasion remains a residual model-level risk.
References
- GHSA-43hx-xm7w-3mhj on OSV.dev
- Web: https://github.com/memtomem/memtomem-stm/security/advisories/GHSA-43hx-xm7w-3mhj
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-77332
- Web: https://github.com/memtomem/memtomem-stm/commit/3d50ba61cbfafba6db261e35c18eed0c3805b390
- Package: https://github.com/memtomem/memtomem-stm
- Web: https://github.com/memtomem/memtomem-stm/releases/tag/v0.1.34
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.