ZeroHour

CVE-2026-82283

IDOR in VoltAgent Memory API Lets Authenticated Users Access Other Users' Conversations

CVSS 4.0
8.6 high
EPSS
<1%p15
Published
()
Modified
AI analysis

VoltAgent through version 2.1.20 fails to validate conversation ownership in its memory API handlers, a broken object-level authorization flaw (CWE-639). An authenticated user can trigger the flaw by supplying caller-controlled conversation or message identifiers to memory endpoints, without any ownership check. This allows the attacker to read, modify, and delete arbitrary conversations and messages belonging to other users on the same deployment. Any deployment running VoltAgent 2.1.20 or earlier, where the memory API is reachable by multiple users, is affected. There is no known public proof-of-concept, the flaw is not in CISA KEV, and EPSS currently estimates only a 0.2% probability of exploitation within 30 days.

What to do: Upgrade to a VoltAgent release newer than 2.1.20 once a patched version is published, and monitor the vendor's advisory for the fixed version. Until then, restrict access to memory API endpoints, enforce conversation-ownership checks at the application layer (e.g., in middleware or API gateways), and review logs for authenticated users accessing conversations they do not own.

Affected
VoltAgentthrough 2.1.20 (all versions up to and including 2.1.20)
Estimated exposure
No basis for an estimate.

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description

VoltAgent through 2.1.20 fails to validate conversation ownership in memory API handlers, allowing authenticated users to access other users' conversations. Attackers can read, modify, and delete arbitrary conversations and messages by supplying caller-controlled identifiers to memory endpoints.

Weakness
CWE-639
Vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

In the news

No ingested article mentions this CVE yet.