What is CVE-2026-13511?
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.
The record classifies CVE-2026-13511 under weakness classes CWE-285, CWE-266. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 144 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 3.1 — LOW
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R - CVSS v4.0 base score
- 2.3
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P - EPSS (FIRST)
- 0.2% probability of exploitation in the next 30 days, higher than 12.4% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-06-28
Is CVE-2026-13511 being exploited?
It currently carries a trending score of 33 in the Threadlinqs vulnerability feed.
Affected products and versions
- (vendor unspecified): VoltAgent
How to fix CVE-2026-13511
Patch reference: https://github.com/VoltAgent/voltagent/pull/1317. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2026-13511
No threat campaign in the Threadlinqs corpus currently references CVE-2026-13511, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, GitHub Security Advisories, FIRST EPSS.