Skip to main content
VulnerabilityPublished

CVE-2026-13508: khoj · Incorrect Authorization

Affects khojSource CVE Database V5

0
Compare

Public exploit available · CVSS 5.1 Medium.

Data as of 11 Nov 2026, 23:24 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
khoj-aikhojAffected
  • 2.0.0-beta.0 – 2.0.0-beta.28
29 affected builds
Fixed in–
GitHubkhoj-ai/khojpkg:github/khoj-ai/khojOther threatsAffected
  • 2.0.0-beta.0 – 2.0.0-beta.28
29 affected builds
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:khoj-ai:khoj:*:*:*:*:*:*:*:*

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

AI-suggested

A pull request with a fix exists but is not yet accepted. Users should monitor the vendor's repository or advisory channels for the acceptance and release of the fix. Until then, consider restricting access to the affected component or applying temporary access controls if feasible.

Description

A flaw has been found in khoj-ai khoj up to 2.0.0-beta.28. This impacts an unknown function of the file src/khoj/routers/api_chat.py of the component Conversation Sharing Handler. This manipulation of the argument conversation.agent causes incorrect authorization. Remote exploitation of the attack is possible. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.

References

Community reviews

Loading reviews…