# CVE-2026-82284: Quivr Chat Endpoints Missing Ownership Validation

> Authenticated attackers can access, delete, or modify other users' chat histories and inject messages due to missing ownership validation.

- **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-3j2c-qqcf-39m8

## What is CVE-2026-82284?

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

### Official description

Quivr versions through 0.0.322 fail to validate chat ownership in the GET /chat/{chat_id}/history, DELETE /chat/{chat_id}, and POST /chat/{chat_id}/question/answer endpoints. Authenticated attackers can read other users' conversation histories including private knowledge base content, delete arbitrary chats, and inject fabricated messages into other users' conversations.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-82284 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82284 is a high-severity missing authorization vulnerability in QuivrHQ quivr, 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-82284 exists.

Affected product: QuivrHQ quivr. 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-82284/ (Markdown: https://insights.sbomify.com/CVE-2026-82284/index.md)
```

## Sources

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

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