Security readout for executives and security teams
Plain-English summary
DeepCode has an unauthenticated file-read flaw in its web UI backend. A remote attacker may request specially encoded paths and read files outside the intended frontend directory. If DeepCode is exposed near sensitive host files, this could disclose credentials, certificates, or application secrets.
Executive priority
Treat this as a high-priority exposure review. The issue can disclose secrets without authentication, but urgency depends on whether DeepCode is deployed, reachable, and able to read sensitive local files.
Technical view
CVE-2026-32847 is a CWE-22 path traversal in new_ui/backend/main.py SPA catch-all route GET /{full_path:path}. The sources state encoded slashes and dot segments can bypass Starlette path normalization and traverse outside FRONTEND_DIST. CVSS v4.0 is 8.7 high, with network access, low complexity, no privileges, and no user interaction.
Likely exposure
Highest exposure is internet- or intranet-accessible DeepCode UI deployments through commit c991dc2 or reported as 1.2.0. The affected version metadata is limited and inconsistent, so teams should confirm exact deployed commits and packaging.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Public advisories describe a remotely reachable unauthenticated file-read condition using encoded path segments, but no cited source confirms exploitation in the wild.
Researcher notes
Evidence supports arbitrary file read, not code execution or write access. Affected-version data needs validation because the bundle references DeepCode 1.2.0, commit c991dc2, and affected versions listed as 0/0. Do not assume a vendor patch unless confirmed by HKUDS or advisory updates.
Mitigation direction
- Check HKUDS DeepCode guidance and update when a fixed release or commit is available.
- Remove public access to DeepCode UI until exposure is confirmed safe.
- Require authentication or network allowlisting in front of the backend.
- Avoid running DeepCode with access to host secrets or broad filesystem permissions.
- Monitor advisory sources for corrected affected-version and patch details.
Validation and detection
- Inventory all DeepCode deployments, container images, and source commits.
- Confirm whether new_ui/backend/main.py includes the vulnerable catch-all route.
- Review access logs for suspicious encoded traversal requests.
- Check whether the runtime can read SSH keys, TLS keys, or application secrets.
- Document any exposed files and rotate affected credentials if disclosure is plausible.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-32847 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: 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
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/HKUDS/DeepCode/issues/126CVE reference, VulnCheck · issue-tracking
- https://www.vulncheck.com/advisories/deepcode-path-traversal-via-spa-catch-all-route-in-main-pyCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.