CVE-2025-69207VulnerabilityPublished 2 Feb 2026

CVE-2025-69207: khoj · Insecure Direct Object Reference

Affects khojSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium : upgrade to 2.0.0-beta.23 when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.0.0-beta.23

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade khoj to 2.0.0-beta.23.

Affected software

Product	Affected	Fixed in
khoj-aikhoj	Affected <2.0.0-beta.23	Fixed in 2.0.0-beta.23
GitHubkhoj-ai/khoj`pkg:github/khoj-ai/khoj`Other threats	Affected =2.0.0-beta.23	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade khoj to version 2.0.0-beta.23 or later where the vulnerability is fixed. Until upgrading, restrict access to the OAuth callback endpoint and monitor logs for suspicious manipulation of the state parameter. Implement strict controls on sharing AI-generated content that may leak user UUIDs, including sanitizing or anonymizing shared data. Employ network segmentation and access controls to limit exposure of the Khoj application to trusted users only. Conduct regular audits of OAuth integrations and verify that authorization flows properly validate user identity. Educate users about the risks of sharing AI-generated images or conversations that might reveal sensitive identifiers. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block unusual OAuth callback requests. Finally, maintain an incident response plan to quickly address any signs of compromise related to this vulnerability.

Description

CVE-2025-69207 is an authorization bypass vulnerability in khoj-ai's self-hosted AI app prior to version 2.0.0-beta.23. The flaw is an Insecure Direct Object Reference (IDOR) in the Notion OAuth callback endpoint, allowing attackers to hijack any user's Notion integration by manipulating the state parameter. Exploitation requires knowledge of the victim's UUID, which can be leaked through shared conversations containing AI-generated images. Successful exploitation enables attackers to replace victims' Notion configurations with their own, causing data poisoning and unauthorized access to the victim's Khoj search index. The vulnerability has a CVSS score of 5.4 (medium severity) and does not require privileges but does require user interaction. No known exploits are currently in the wild.

Impact

For European organizations using khoj-ai's khoj application integrated with Notion, this vulnerability poses a risk of unauthorized access to sensitive internal data indexed by Khoj. Attackers could manipulate or poison search indexes, leading to misinformation or exposure of confidential information. This could disrupt business operations relying on accurate AI search results and potentially leak intellectual property or personal data. Since the attack requires knowledge of user UUIDs, organizations that share AI-generated content publicly or internally without proper controls risk leaking these identifiers. The impact extends to data integrity and availability, as poisoned data could degrade trust in AI-driven workflows. Given the medium CVSS score, the threat is moderate but significant for organizations relying heavily on Khoj for knowledge management. The lack of known exploits suggests limited current risk, but the vulnerability should be addressed promptly to prevent future attacks.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Feb 2026, 11:06 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats