Cross-tenant chat disclosure and tampering via unchecked identifiers
Published Aug 28, 2026 · Updated Aug 28, 2026
Broken object-level authorization in Quivr through 0.0.322 allows remote authenticated users to read, alter, or delete other users' chats. Three chat routes accept a caller-supplied chat_id and query or mutate by that identifier without binding it to the authenticated user's ID. Any regular account with a target chat UUID can retrieve histories containing private knowledge-base content, delete the chat, or persist fabricated question-and-answer pairs.
Summary
What happened
Broken object-level authorization in Quivr through 0.0.322 allows remote authenticated users to read, alter, or delete other users' chats. Three chat routes accept a caller-supplied chat_id and query or mutate by that identifier without binding it to the authenticated user's ID. Any regular account with a target chat UUID can retrieve histories containing private knowledge-base content, delete the chat, or persist fabricated question-and-answer pairs.
The record
- CVE
- CVE-2026-82284
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- Quivr
- Product
- Quivr
- Classifications
- CWE-639
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.0.322
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Quivr chat IDOR reproduction stepsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo