Kotaemon through 0.12.0 fails to properly validate conversation ownership in select_conv, delete_conv, rename_conv, and on_set_public_conversation functions in control.py. Attackers can read other users' chat histories, delete conversations, or rename conversations by supplying arbitrary conversation identifiers without proper authorization checks.
CVE-2026-82281
Score 7.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-28. a secondary CVSS source baseline 7.4; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.4
- EG Score
- 7.4(high)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity74% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
August 28, 2026
Last Modified
August 28, 2026
Advisory Details (4)
Auto-updated Aug 28, 2026Kotaemon Missing Ownership Check in Conversation Functions | Advisories | VulnCheck
https://www.vulncheck.com/advisories/kotaemon-missing-ownership-check-in-conversation-functionskotaemon/libs/ktem/ktem/pages/chat/control.py at 9ad3e4e49aa35b8acddd235918a5d9753c1cfdf9 · Cinnamon/kotaemon · GitHub
https://github.com/Cinnamon/kotaemon/blob/9ad3e4e49aa35b8acddd235918a5d9753c1cfdf9/libs/ktem/ktem/pages/chat/control.pyGitHub - Cinnamon/kotaemon: An open-source RAG-based tool for chatting with your documents. · GitHub
https://github.com/Cinnamon/kotaemonCross-User Conversation IDOR -- Unauthenticated Read and Authenticated Delete of Any Conversation · Issue #846 · Cinnamon/kotaemon · GitHub
https://github.com/Cinnamon/kotaemon/issues/846Vendor Advisories for CVE-2026-82281(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 20:37 UTCGHSA enrichment
- 2026-08-29 08:30 UTCEG score recompute
- 2026-08-29 08:30 UTCGHSA enrichment
- 2026-08-28 20:25 UTCEG score recompute
- 2026-08-28 19:40 UTCEG score recompute
- 2026-08-28 19:36 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS p94CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS p95CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS p97CRITICAL
- CVE-2019-13360EG 9.8EPSS p97CRITICAL
- CVE-2019-12866EG 9.8CRITICAL
- CVE-2019-9756EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-82281?
When was CVE-2026-82281 disclosed?
Is CVE-2026-82281 actively exploited?
What is the CVSS score of CVE-2026-82281?
How do I remediate CVE-2026-82281?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82281
Is Your Infrastructure Affected by CVE-2026-82281?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.