Prompt hijacking via missing object ownership checks
Published Aug 28, 2026 · Updated Aug 28, 2026
Authorization bypass in Quivr 0 through 0.0.322 allows remote authenticated users to read and overwrite prompts by UUID. The backend GET and PUT prompt routes pass an attacker-selected prompt_id to service operations without checking ownership or brain affiliation. Read-only members can obtain prompt identifiers from shared-brain details and replace a system prompt, altering subsequent responses for every user of that brain.
Summary
What happened
Authorization bypass in Quivr 0 through 0.0.322 allows remote authenticated users to read and overwrite prompts by UUID. The backend GET and PUT prompt routes pass an attacker-selected prompt_id to service operations without checking ownership or brain affiliation. Read-only members can obtain prompt identifiers from shared-brain details and replace a system prompt, altering subsequent responses for every user of that brain.
The record
- CVE
- CVE-2026-82280
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- Quivr
- Product
- Quivr
- Classifications
- CWE-639, T1565.001
- 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?
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 prompt 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