# CVE-2026-75337: Path traversal in n/a

> Anonymous attackers can read arbitrary files outside the preview root via path traversal in the static resource interface.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-5xh8-pmj2-f75q

## What is CVE-2026-75337?

CVE-2026-75337 is a critical path traversal vulnerability in n/a, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The static resource interface /api/static/{deployKey}/ of Yu AI Code Mother v4.3 is vulnerable to path traversal. The user-controlled path is concatenated to the preview root directory without any normalization, allowing anonymous attackers to read files outside the preview root.

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

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


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

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

## Is CVE-2026-75337 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75337 is a critical path traversal vulnerability in n/a, published on 27 Aug 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-75337 exists.

Affected product: n/a. 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-75337/ (Markdown: https://insights.sbomify.com/CVE-2026-75337/index.md)
```

## Sources

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

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