Skip to main content
Menu
CVEs

memtomem-stm unescaped memory fields inject Markdown into agent context

CVE-2026-77332Published , updated

2.3LowCNA
Exploited
No known exploitation
Fix
Fixed in 0.1.34
Who is exposed
Not reported

Summary

memtomem-stm, a short-term memory proxy gateway for AI agents, does not treat untrusted long-term and working-memory fields as inert data, so a crafted memory can add Markdown or HTML-style structure to surfaced memory context. An attacker with low-privilege network access can do this without any user action, creating misleading structural boundaries or hiding surfaced content, which can change how a consuming agent interprets the memory.

Written by a model

Original description

memtomem-stm is a short-term memory proxy gateway with proactive memory surfacing for AI agents. From 0.1.0 until 0.1.34, untrusted long-term and working-memory fields can introduce Markdown or HTML-compatible structure into the surfaced-memory envelope because those fields are not serialized as inert data. A crafted memory can create misleading structural boundaries or visually conceal surfaced content, affecting how a consuming agent interprets the memory context. Ordinary natural-language persuasion remains a residual model-level risk and is outside the structural serialization flaw. This issue is fixed in version 0.1.34.

What to do

Upgrade to a fixed version: 0.1.34.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-77332 (memtomem-stm: Surfaced memory data can escape the Markdown compatibility boundary), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-77332 (entry last updated 2026-11-20):
Affected:
- memtomem memtomem-stm: from 0.1.0, fixed in 0.1.34
Fixed versions: 0.1.34.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-77332 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77332 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/memtomem/memtomem-stm/security/advisories/GHSA-43hx-xm7w-3mhj
- https://github.com/memtomem/memtomem-stm/commit/3d50ba61cbfafba6db261e35c18eed0c3805b390
- https://github.com/memtomem/memtomem-stm/releases/tag/v0.1.34
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-77332
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77332"}.

Affected versions

cve.now Index

5Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity2.3/10CVSS 2.3
  • No patch0/5No signal

What would change the score

  • Would score about 60 if added to CISA KEV
  • Would score about 55 if CISA's SSVC rates exploitation active
  • Would score about 24 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · memtomem/memtomem-stm · Advisory GHSA-43hx-xm7w-3mhj
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-77332
RecordNVD · CVE-2026-77332
Other links 2
RepositoryGitHub · memtomem/memtomem-stm · Commit 3d50ba61
RepositoryGitHub · memtomem/memtomem-stm · Release v0.1.34

Questions about CVE-2026-77332

Is CVE-2026-77332 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-77332?

memtomem-stm: from 0.1.0 before 0.1.34.

Source: cve.now feed data

How do I fix CVE-2026-77332?

Upgrade to a fixed version: 0.1.34.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.