cve.bz

CVE-2025-69207 khoj khoj

7.1 highExploit referenceEPSS 0.4%Fix available

High (7.1) in khoj khoj. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Khoj is a self-hostable artificial intelligence app. Prior to 2.0.0-beta.23, an IDOR in the Notion OAuth callback allows an attacker to hijack any user's Notion integration by manipulating the state parameter. The callback endpoint accepts any user UUID without verifying the OAuth flow was initiated by that user, allowing attackers to replace victims' Notion configurations with their own, resulting in data poisoning and unauthorized access to the victim's Khoj search index. This attack requires knowing the user's UUID which can be leaked through shared conversations where an AI generated image is present. This vulnerability is fixed in 2.0.0-beta.23.

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 37th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-02-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-69207 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-69207?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-69207?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-69207 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
khoj:khojbefore 2.0.0
khoj:khoj2.0.0:beta1
khoj:khoj2.0.0:beta10
khoj:khoj2.0.0:beta11
khoj:khoj2.0.0:beta12
khoj:khoj2.0.0:beta13
khoj:khoj2.0.0:beta14
khoj:khoj2.0.0:beta15
khoj:khoj2.0.0:beta16
khoj:khoj2.0.0:beta17
khoj:khoj2.0.0:beta18
khoj:khoj2.0.0:beta19
khoj:khoj2.0.0:beta2
khoj:khoj2.0.0:beta20
khoj:khoj2.0.0:beta21
khoj:khoj2.0.0:beta22

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6whj-7qmg-86qjPyPIkhoj<=2.0.0b25.dev3no fix published
PYSEC-2026-1491PyPIkhoj<=2.0.0b25.dev3no fix published

References

Check your stackJSON