Search-index poisoning via user-controlled OAuth state
Published Feb 2, 2026 · Updated Feb 2, 2026
Authorization bypass in Khoj before 2.0.0-beta.23 allows remote attackers to replace a victim's Notion integration via OAuth state. The callback resolves the state parameter as an arbitrary user UUID, deletes that user's Notion configuration, and stores the attacker's token without binding the flow to the authenticated session. Exploitation requires the victim UUID, exposed by shared conversations with AI-generated images, and permits poisoning content in the victim's search index.
Summary
What happened
Authorization bypass in Khoj before 2.0.0-beta.23 allows remote attackers to replace a victim's Notion integration via OAuth state. The callback resolves the state parameter as an arbitrary user UUID, deletes that user's Notion configuration, and stores the attacker's token without binding the flow to the authenticated session. Exploitation requires the victim UUID, exposed by shared conversations with AI-generated images, and permits poisoning content in the victim's search index.
The record
- CVE
- CVE-2025-69207
- Published
- Feb 2, 2026
- Updated
- Feb 2, 2026
- Vendor
- Khoj AI
- Product
- Khoj
- Classifications
- CWE-639, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 2, 2026CVE publishedPublication date reported by the CVE source.
- Feb 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.0.0-beta.23
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Vendor advisory callback proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo