Skip to main content
EPSS 0.3%top 79%

VoltAgent through 2.1.20 fails to validate conversation ownership in memory API handlers, allowing authenticated users to access other users'… (CVE-2026-82283)

0
High
Published: 08/28/2026 (08/28/2026, 21:31:27 UTC)
Source: GCVE Database

Description

VoltAgent versions through 2.1.20 contain a vulnerability where conversation ownership is not properly validated in memory API handlers. This flaw allows authenticated users to access, read, modify, and delete conversations and messages belonging to other users by manipulating caller-controlled identifiers.

CVSS v3.1

Score 8.1high

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected software

Affected versions
<=2.1.20

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/08/2026, 02:07:05 UTC

Technical Analysis

CVE-2026-82283 describes a security vulnerability in VoltAgent up to version 2.1.20. The issue arises from a failure to validate conversation ownership within memory API handlers. Authenticated users can exploit this to access arbitrary conversations and messages by supplying identifiers they control, leading to unauthorized read, modification, and deletion of data. The vulnerability is classified under CWE-639 (Authorization Bypass Through User-Controlled Key). The CVSS v3.1 base score is 8.1, indicating a high severity with network attack vector, low attack complexity, requiring privileges, no user interaction, unchanged scope, and high confidentiality and integrity impacts but no availability impact.

Potential Impact

An attacker with valid authentication can bypass authorization checks to access and manipulate conversations and messages of other users. This compromises confidentiality and integrity of user data but does not affect availability. There are no known exploits in the wild at this time.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict access to the affected API endpoints to trusted users only and monitor for suspicious activity related to conversation access. Avoid exposing memory API handlers to untrusted authenticated users.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-ch6f-pcf5-xp4j
Osv Schema Version
1.4.0
Aliases
["CVE-2026-82283"]
Database Specific Severity
HIGH
Cvss Version
3.1

Threat ID: 6a92f7e8acd9273b49e75eeb

Added to database: 08/29/2026, 15:16:56 UTC

Last enriched: 09/08/2026, 02:07:05 UTC

Last updated: 10/12/2026, 06:48:19 UTC

Views: 22

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses