Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

khoj has an unauthenticated path traversal in /home/ endpoint that allows file read from server filesystem

GHSA-62mm-xwmv-crhg

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (khoj 2.0.0b25), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI khoj

    Affected
    >= 2.0.0b23, < 2.0.0b25
    Fixed in
    2.0.0b25

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary The /home/{filepath:path} endpoint in webclient.py serves static files by directly concatenating the user-supplied filepath with the homedirectory constant. There is no path traversal filtering, no path normalization check, and no authentication required. An attacker can use ../ sequences to read arbitrary files from the server filesystem. Details Vulnerable code — src/khoj/routers/webclient.py lines 46-49: Where homedirectory is defined in src/khoj/utils/constants.py line 6: What is missing: - No .. traversal filtering - No path normalization/resolution check (e.g., resolved.isrelativeto(homedirectory)) - No authentication decorator (@requires(["authenticated"]) is absent) - Starlette's FileResponse does NOT perform path traversal protection Path resolution: PoC URL-encoded variant (may bypass some reverse proxy normalization): Impact Unauthenticated arbitrary file read. An attacker with network access to the Khoj instance can: - Read application configuration — Django…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-62mm-xwmv-crhg

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from ghsa record GHSA-62mm-xwmv-crhg

Agent brief

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

# Patch Next advisory brief: GHSA-62mm-xwmv-crhg

Advisory: khoj has an unauthenticated path traversal in /home/ endpoint that allows file read from server filesystem
IDs: GHSA-62mm-xwmv-crhg
Record: https://patchnext.com/advisories/ghsa-62mm-xwmv-crhg (revision 3, source checked 26 Oct 2026, 13:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: khoj 2.0.0b25. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI khoj: affected >= 2.0.0b23, < 2.0.0b25; fixed in 2.0.0b25

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## 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://github.com/advisories/GHSA-62mm-xwmv-crhg (GitHub-reviewed advisory GHSA-62mm-xwmv-crhg lists affected ranges: PyPI khoj >=2.0.0-beta.23 <2.0.0-beta.25)
- Verified: https://github.com/advisories/GHSA-62mm-xwmv-crhg (GitHub-reviewed advisory GHSA-62mm-xwmv-crhg lists affected ranges: PyPI khoj >=2.0.0b23 <2.0.0b25)

Commands are suggestions: review each one before running it.

Loading voting…