Khoj has an IDOR in Notion OAuth Flow that Enables Index Poisoning

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2025-69207: 0.41% estimated exploitation activity in the next 30 days; percentile 35.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details When users share conversations which contain AI generated images, the file path for the image is constructed using the user's UUID. Knowing this UUID, an attacker is able to intercept the OAuth callback for Notion and replace the state parameter with the other user's UUID and sync notion onto their account. PoC The vulnerable line of code exists in src/khoj/routers/notion.py on the callback endpoint. To exploit is relatively easy. Once we…

Published by the source

2 Feb 2026, 17:31 UTC

Last modified by the source

7 Jul 2026, 17:57 UTC

Source last checked

26 Oct 2026, 13:36 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-6whj-7qmg-86qj

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-6whj-7qmg-86qj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-69207

Advisory: Khoj has an IDOR in Notion OAuth Flow that Enables Index Poisoning
IDs: CVE-2025-69207, GHSA-6whj-7qmg-86qj
Record: https://patchnext.com/advisories/cve-2025-69207 (revision 2, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI khoj: affected <= 2.0.0b25.dev3

## Suggested inspection (read-only)
- `python -m pip show khoj`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on khoj.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6whj-7qmg-86qj (OSV record GHSA-6whj-7qmg-86qj lists affected ranges: PyPI khoj >=0 <=2.0.0b25.dev3)
- Verified: https://github.com/advisories/GHSA-6whj-7qmg-86qj (GitHub-reviewed advisory GHSA-6whj-7qmg-86qj lists affected ranges: PyPI khoj >=0 <=2.0.0b25.dev3)

Commands are suggestions: review each one before running it.