Vulnerability in Quivr (CVE-2026-82284)
Summary
Vulnerability in Quivr (CVE-2026-82284). Confidential information can be exposed externally. Exploitable via GET /chat/{chat_id}/history.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-82284 has been found in Quivr.
Attackers can target a specific entry point like GET /chat/{chat_id}/history over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Quivr CVE-2026-82284" on the vendor's site.
CVE-2026-82284 (Quivr) — CWE-639 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /chat/{chat_id}/history / DELETE /chat/{chat_id} / POST /chat/{chat_id}/question/answer
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in Quivr. Attackers reach the vulnerable code path via GET /chat/{chat_id}/history.
Check the vendor advisory for the affected versions of Quivr. Attack surface: GET /chat/{chat_id}/history / DELETE /chat/{chat_id} / POST /chat/{chat_id}/question/answer.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /chat/{chat_id}/history requests with malformed payloads or SQL meta-characters. Run grep -r 'Quivr' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Quivr' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Quivrを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /chat/{chat_id}/history' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /chat/{chat_id}/historyへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /chat/{chat_id}/history on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- report github.com
- web github.com
- web github.com