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.
CVE-2026-82283
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. a secondary CVSS source baseline 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(high)
- EG Risk
- 52(Track*)EG Risk 52/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 15%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (4)
Auto-updated Aug 28, 2026VoltAgent Memory API Handlers Missing Ownership Checks | Advisories | VulnCheck
https://www.vulncheck.com/advisories/voltagent-memory-api-handlers-missing-ownership-checksvoltagent/packages/server-core/src/handlers/memory.handlers.ts at 44b4c8e4998ce56095b2f0e4eaf1a988f5e6d0de · VoltAgent/voltagent · GitHub
https://github.com/VoltAgent/voltagent/blob/44b4c8e4998ce56095b2f0e4eaf1a988f5e6d0de/packages/server-core/src/handlers/memory.handlers.tsGitHub - VoltAgent/voltagent: AI Agent Engineering Platform built on an Open Source TypeScript AI Agent Framework · GitHub
https://github.com/VoltAgent/voltagentMemory API Missing Ownership Check -- Cross-User Conversation Access (IDOR) in @voltagent/server-hono · Issue #1371 · VoltAgent/voltagent · GitHub
https://github.com/VoltAgent/voltagent/issues/1371Vendor Advisories for CVE-2026-82283(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 22:32 UTCGHSA enrichment
- 2026-08-29 10:40 UTCGHSA enrichment
- 2026-08-28 22:48 UTCEG score recompute
- 2026-08-28 22:48 UTCGHSA enrichment
- 2026-08-28 22:09 UTCEG score recompute
- 2026-08-28 22:09 UTCGHSA enrichment
- 2026-08-28 20:25 UTCEG score recompute
- 2026-08-28 19:39 UTCEG score recompute
- 2026-08-28 19:36 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-82283?
When was CVE-2026-82283 disclosed?
Is CVE-2026-82283 actively exploited?
What is the CVSS score of CVE-2026-82283?
How do I remediate CVE-2026-82283?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82283
Is Your Infrastructure Affected by CVE-2026-82283?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.