A vulnerability was determined in VoltAgent up to 2.1.17. Affected by this issue is the function handleGetMemoryConversation of the file packages/server-core/src/handlers/memory.handlers.ts of the component Memory REST API. Executing a manipulation of the argument conversationId can lead to improper authorization. The attack may be performed from remote. This attack is characterized by high complexity. The exploitation is known to be difficult. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.
CVE-2026-13511
Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-06-29. a secondary CVSS source baseline 3.1; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.1
- EG Score
- 3.1(high)
- EPSS
- 12.5%
- KEV
- Not listed
Published
June 28, 2026
Last Modified
June 29, 2026
References (7)
- cna@vuldbhttps://github.com/VoltAgent/voltagent/
- cna@vuldbhttps://github.com/VoltAgent/voltagent/issues/1315
- cna@vuldbhttps://github.com/VoltAgent/voltagent/pull/1317
- cna@vuldbhttps://vuldb.com/cve/CVE-2026-13511
- cna@vuldbhttps://vuldb.com/submit/838873
- cna@vuldbhttps://vuldb.com/vuln/374519
- cna@vuldbhttps://vuldb.com/vuln/374519/cti
Vendor Advisories for CVE-2026-13511(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 18× 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-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 14:03 UTCEG score recompute
- 2026-07-04 14:02 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 18:16 UTCEG score recompute
- 2026-07-01 18:15 UTCGHSA enrichment
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 15:26 UTCNVD updateCVSS v4 → 1.3
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 13:32 UTCMITRE cvelistV5CVSS v4 → 2.3
- 2026-06-29 00:03 UTCNVD updateCVSS v4 → 1.3
- 2026-06-28 22:38 UTCEG score recompute
- 2026-06-28 22:37 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-13511?
When was CVE-2026-13511 disclosed?
Is CVE-2026-13511 actively exploited?
What is the CVSS score of CVE-2026-13511?
How do I remediate CVE-2026-13511?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-13511
Is Your Infrastructure Affected by CVE-2026-13511?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.