1-minute read
What a defender needs to know
A signed-in user of a Kotaemon multi-user instance can use another person’s conversation UUID to read chat transcripts and retrieval history or delete, rename, and alter suggested prompts in that conversation. CERT/CC identifies v0.12.0 and earlier as affected. The retrieval history may include verbatim excerpts of private documents. Public conversations expose UUIDs in the global browser, and moving one to private preserves its ID. The CVE record for CVE-2026-86867 identifies four handlers in libs/ktem/ktem/pages/chat/control.py that look up a conversation by ID without checking Conversation.user against user_id.
Find multi-user deployments, their installed versions, allowed accounts, and conversations containing sensitive material. Reduce access to mutually trusted users, remove unnecessary accounts, and restrict network reachability while evaluating an owner-checking fix; CERT/CC reported no official patch on September 23. Correlate account IDs, conversation UUIDs, and owners in retained request telemetry to investigate cross-owner actions. If those records are unavailable, use the account and conversation inventory to scope exposure. Once a fix is installed, test with two accounts and separate non-sensitive conversations: each owner retains access, and cross-owner reads, deletes, renames, and suggestion changes are denied by the server.