# CVE-2026-38360: dash-uploader has a directory traversal vulnerability

> A remote attacker can execute arbitrary code via a directory traversal vulnerability in the dash-uploader Python library.

- **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:** 8 May 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-3rf6-x59v-5jfv, PYSEC-2026-320

## What is CVE-2026-38360?

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

### Official description

Directory Traversal vulnerability in fohrloop dash-uploader v.0.1.0 through v.0.7.0a2 allows a remote attacker to execute arbitrary code via the dash_uploader/httprequesthandler.py, BaseHttpRequestHandler.get_temp_root(), BaseHttpRequestHandler._post() components.

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

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

3 open source packages ship an affected version, including dash-uploader.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dash-uploader` | PyPI | From 0.1.0 to 0.7.0a2 | None |
| `dash-uploader` | PyPI | From 0.1.0 to 0.7.0a2 | None |
| `dash-uploader` | PyPI | From 0.1.0 to 0.7.0a2 | None |

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

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

## Is CVE-2026-38360 being exploited?

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

Public exploit code:

- Advisory: CVE-2026-38360 path traversal (CWE-22) in dash-uploader (Python/PyPI) (github_poc): https://github.com/a1ohadance/CVE-2026-38360
- dash-uploader 0.1.0 - 0.7.0a2 - Unauthenticated Arbitrary File Write via Path Traversal (nuclei): http/cves/2026/CVE-2026-38360.yaml

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- dash-uploader (PyPI): affected from 0.1.0 up to 0.7.0a2; no fix listed
- dash-uploader (PyPI): affected from 0.1.0 up to 0.7.0a2; no fix listed
- dash-uploader (PyPI): affected from 0.1.0 up to 0.7.0a2; no fix listed

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

## Sources

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

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