khoj-ai khoj up to 2.0.0-beta.22 Callback Endpoint state authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in khoj-ai khoj up to 2.0.0-beta.22. It has been rated as problematic. Affected by this issue is some unknown functionality of the component Callback Endpoint. This manipulation of the argument state causes authorization. This vulnerability is handled as CVE-2025-69207. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in khoj-ai khoj up to 2.0.0-beta.22. It has been declared as problematic. Affected by this vulnerability is an unknown function of the component Callback Endpoint. The manipulation of the argument state with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. 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. As an impact it is known to affect integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is known as CVE-2025-69207 since 12/29/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading to version 2.0.0-beta.23 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 1b7ccd141d47f365edeccc57d7316cb0913d748b is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 2.0.0-beta.0
- 2.0.0-beta.1
- 2.0.0-beta.2
- 2.0.0-beta.3
- 2.0.0-beta.4
- 2.0.0-beta.5
- 2.0.0-beta.6
- 2.0.0-beta.7
- 2.0.0-beta.8
- 2.0.0-beta.9
- 2.0.0-beta.10
- 2.0.0-beta.11
- 2.0.0-beta.12
- 2.0.0-beta.13
- 2.0.0-beta.14
- 2.0.0-beta.15
- 2.0.0-beta.16
- 2.0.0-beta.17
- 2.0.0-beta.18
- 2.0.0-beta.19
- 2.0.0-beta.20
- 2.0.0-beta.21
- 2.0.0-beta.22
License
Website
- Product: https://github.com/khoj-ai/khoj/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 5.9
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.1
NVD Vector: 🔒
CNA Base Score: 5.4
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: khoj 2.0.0-beta.23
Patch: 1b7ccd141d47f365edeccc57d7316cb0913d748b
Timeline
12/29/2025 CVE reserved02/03/2026 Advisory disclosed
02/03/2026 VulDB entry created
02/27/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-6whj-7qmg-86qj
Status: Confirmed
CVE: CVE-2025-69207 (🔒)
GCVE (CVE): GCVE-0-2025-69207
GCVE (VulDB): GCVE-100-343861
Entry
Created: 02/03/2026 07:58Updated: 02/27/2026 23:44
Changes: 02/03/2026 07:58 (69), 02/27/2026 23:44 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.