# An issue 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, dash_uploader/upload.py in the Upload fu...

Advisory record · `PYSEC-2026-37`

- **Identifiers:** `PYSEC-2026-37` · `CVE-2026-38361`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html) · [CWE-670](https://cwe.mitre.org/data/definitions/670.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) · [CWE-670](https://agentprime.io/advisories/tag/cwe-670.md)
- **Published:** 8 May 2026
- **Updated:** 20 May 2026
- **Reviewed by a person:** No

Published by OSV at 8 May 2026, 15:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `dash-uploader` (PyPI): affected `>=0.1.0, <0.7.0a1`; fixed in `0.7.0a1`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from OSV

- **CISA KEV:** Not listed.
- **EPSS:** 0.026, the 85th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of OSV, published 8 May 2026. New records show when each source confirmed them.

## Sources

- [OSV: PYSEC-2026-37](https://osv.dev/vulnerability/PYSEC-2026-37)
- <https://docs.python.org/3/library/functions.html#all>
- <https://github.com/fohrloop/dash-uploader/blob/stable/dash_uploader/httprequesthandler.py>
- <https://libraries.io/pypi/dash-uploader>
- <https://pepy.tech/project/dash-uploader>
- <https://pypistats.org/packages/dash-uploader>
- <https://github.com/fohrloop/dash-uploader>
- <https://pypi.org/project/dash-uploader/>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/PYSEC-2026-37>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/PYSEC-2026-37/>. Everything for agents: <https://agentprime.io/llms.txt>.
