CVE-2026-13508Public exploitNetwork attack vector

Cross-user private agent use via unauthorized fork

Published Jun 28, 2026 · Updated Jun 28, 2026

Incorrect authorization in Khoj 2.0.0-beta.0 through 2.0.0-beta.28 allows remote authenticated users to use another user's private agent. The share flow stores conversation.agent in a public conversation, and the fork flow copies it into the recipient's conversation without reauthorizing access. Exploitation requires one user to share a conversation and another authenticated user to fork it; private agent behavior can cross user boundaries, but normal document search blocks private knowledge retrieval.

CVSS severity5.5
Medium
EPSS probability0.29%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect authorization in Khoj 2.0.0-beta.0 through 2.0.0-beta.28 allows remote authenticated users to use another user's private agent. The share flow stores conversation.agent in a public conversation, and the fork flow copies it into the recipient's conversation without reauthorizing access. Exploitation requires one user to share a conversation and another authenticated user to fork it; private agent behavior can cross user boundaries, but normal document search blocks private knowledge retrieval.

The record

CVE
CVE-2026-13508
Published
Jun 28, 2026
Updated
Jun 28, 2026
Vendor
Khoj AI
Product
Khoj
Classifications
CWE-863, CWE-285
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 28, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 28, 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.

  1. Affected versionversion=2.0.0-beta.0
  2. Affected versionversion=2.0.0-beta.1
  3. Affected versionversion=2.0.0-beta.10
  4. Affected versionversion=2.0.0-beta.11
  5. Affected versionversion=2.0.0-beta.12
  6. Affected versionversion=2.0.0-beta.13
  7. Affected versionversion=2.0.0-beta.14
  8. Affected versionversion=2.0.0-beta.15
  9. Affected versionversion=2.0.0-beta.16
  10. Affected versionversion=2.0.0-beta.17
  11. Affected versionversion=2.0.0-beta.18
  12. Affected versionversion=2.0.0-beta.19
  13. Affected versionversion=2.0.0-beta.2
  14. Affected versionversion=2.0.0-beta.20
  15. Affected versionversion=2.0.0-beta.21
  16. Affected versionversion=2.0.0-beta.22
  17. Affected versionversion=2.0.0-beta.23
  18. Affected versionversion=2.0.0-beta.24
  19. Affected versionversion=2.0.0-beta.25
  20. Affected versionversion=2.0.0-beta.26
  21. Affected versionversion=2.0.0-beta.27
  22. Affected versionversion=2.0.0-beta.28
  23. Affected versionversion=2.0.0-beta.3
  24. Affected versionversion=2.0.0-beta.4
  25. Affected versionversion=2.0.0-beta.5
  26. Affected versionversion=2.0.0-beta.6
  27. Affected versionversion=2.0.0-beta.7
  28. Affected versionversion=2.0.0-beta.8
  29. Affected versionversion=2.0.0-beta.9

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Khoj AI · Khojversion=2.0.0-beta.0; version=2.0.0-beta.1; version=2.0.0-beta.10; version=2.0.0-beta.11; version=2.0.0-beta.12; version=2.0.0-beta.13; version=2.0.0-beta.14; version=2.0.0-beta.15; version=2.0.0-beta.16; version=2.0.0-beta.17; version=2.0.0-beta.18; version=2.0.0-beta.19; version=2.0.0-beta.2; version=2.0.0-beta.20; version=2.0.0-beta.21; version=2.0.0-beta.22; version=2.0.0-beta.23; version=2.0.0-beta.24; version=2.0.0-beta.25; version=2.0.0-beta.26; version=2.0.0-beta.27; version=2.0.0-beta.28; version=2.0.0-beta.3; version=2.0.0-beta.4; version=2.0.0-beta.5; version=2.0.0-beta.6; version=2.0.0-beta.7; version=2.0.0-beta.8; version=2.0.0-beta.9

Published CVSS scores

2.0VulDBCVSS: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
5.5VulDBCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
6.5VulDBAV:N/AC:L/Au:S/C:P/I:P/A:P

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-863Incorrect Authorization
CWE-285Improper Authorization

Public exploit references

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