# CVE-2026-32847: DeepCode 1.2.0 Path Traversal via SPA Catch-All Route in main.py

> Unauthenticated attackers can read arbitrary files, including secrets, via path traversal in the SPA catch-all route of DeepCode.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-2vjv-m9hw-qvjf

## What is CVE-2026-32847?

CVE-2026-32847 is a high-severity path traversal vulnerability in HKUDS DeepCode, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DeepCode through commit c991dc2 contains a path traversal vulnerability in the SPA catch-all route in new_ui/backend/main.py that allows unauthenticated attackers to read arbitrary files by supplying percent-encoded path segments to the GET /{full_path:path} endpoint. Attackers can bypass Starlette's path normalization by encoding slashes as %2F and dots as %2E%2E, causing the joined path to traverse outside FRONTEND_DIST and exposing sensitive files such as SSH private keys, TLS certificates, and application secrets with a single HTTP request.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-32847?

It affects 1 product.


Products: Hkuds Deepcode.

## How do I fix CVE-2026-32847?

No fix has been published for CVE-2026-32847 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-32847 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32847 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32847 and fix it if it is affected.

What it is: CVE-2026-32847 is a high-severity path traversal vulnerability in HKUDS DeepCode, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32847 exists.

Affected product: HKUDS DeepCode. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2026-32847/ (Markdown: https://insights.sbomify.com/CVE-2026-32847/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32847
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32847
- OSV: https://osv.dev/vulnerability/CVE-2026-32847

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32847/
Summaries are generated and may contain mistakes; the official description above is the record.