Skip to main content
Menu
CVEs

memmy-agent information disclosure in Memory HTTP Service logs

CVE-2026-132560Published November 19, 2026, updated

4.8MediumCNA
Exploited
Proof of concept public, per CISA
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

A flaw in the Memory HTTP Service of MemTensor memmy-agent lets an attacker read information they should not see through the /api/v1/memory/logs function. An attacker must already have local access and a low-privilege account, and no user action is needed.

Written by a model

Original description

A flaw has been found in MemTensor memmy-agent up to 1.1.1. This impacts an unknown function of the file /api/v1/memory/logs of the component Memory HTTP Service. This manipulation causes information disclosure. The attack is restricted to local execution. The exploit has been published and may be used. Patch name: 421ce6cb33861255d34c3887d39aced009b3ce9b. It is suggested to install a patch to address this issue.

What to do

Apply the patch listed under Evidence.

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-132560 (MemTensor memmy-agent Memory HTTP Service logs information disclosure), 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-132560 (entry last updated 2026-11-19):
Affected:
- MemTensor memmy-agent: versions 1.1.0, 1.1.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132560 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132560 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/MemTensor/memmy-agent/pull/842
- https://github.com/MemTensor/memmy-agent/commit/421ce6cb33861255d34c3887d39aced009b3ce9b
- https://vuldb.com/vuln/439658
- https://vuldb.com/vuln/439658/cti
- https://vuldb.com/cve/CVE-2026-132560
- https://vuldb.com/submit/1045040
- https://github.com/MemTensor/memmy-agent/
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-132560
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-132560"}.

Affected versions

cve.now Index

20Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity4.8/10CVSS 4.8
  • 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 42 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 10

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-132560
RecordNVD · CVE-2026-132560
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · MemTensor/memmy-agent · Issue #462
Other links 7
AdvisoryVulDB · Advisory #439658
AdvisoryVulDB · Threat intelligence #439658
AdvisoryVulDB · CVE-2026-132560 record
AdvisoryVulDB · Submission #1045040
PatchGitHub · MemTensor/memmy-agent · Pull request #842
PatchGitHub · MemTensor/memmy-agent · Commit 421ce6cb
RepositoryGitHub · MemTensor/memmy-agent · Repository

Questions about CVE-2026-132560

Is CVE-2026-132560 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-132560?

memmy-agent: versions 1.1.0, 1.1.1.

Source: cve.now feed data

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