# CVE-2026-82283: VoltAgent Memory API Handlers Missing Ownership Checks

> Authenticated users can access, modify, and delete other users' conversations due to missing ownership checks in VoltAgent memory API handlers.

- **Severity:** High 8.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-ch6f-pcf5-xp4j

## What is CVE-2026-82283?

CVE-2026-82283 is a high-severity missing authorization vulnerability in voltagent, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-82283?


## How do I fix CVE-2026-82283?

No fix has been published for CVE-2026-82283 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82283 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82283 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82283 and fix it if it is affected.

What it is: CVE-2026-82283 is a high-severity missing authorization vulnerability in voltagent, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82283 exists.

Affected product: voltagent. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82283/ (Markdown: https://insights.sbomify.com/CVE-2026-82283/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82283
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82283
- OSV: https://osv.dev/vulnerability/CVE-2026-82283

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82283/
Summaries are generated and may contain mistakes; the official description above is the record.