# CVE-2025-5173: HumanSignal label-studio-ml-backend PT File neural_nets.py load deserialization

> Local attackers can exploit unsafe deserialization in the PT file handler to execute arbitrary code within the label-studio-ml-backend library.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2025
- **Updated:** 28 May 2025
- **Also known as:** GHSA-55g9-6c2x-gf8q, PYSEC-2026-1505

## What is CVE-2025-5173?

CVE-2025-5173 is a medium-severity unsafe deserialization vulnerability in HumanSignal label-studio-ml-backend, published on 26 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in HumanSignal label-studio-ml-backend up to 9fb7f4aa186612806af2becfb621f6ed8d9fdbaf and classified as problematic. Affected by this vulnerability is the function load of the file label-studio-ml-backend/label_studio_ml/examples/yolo/utils/neural_nets.py of the component PT File Handler. The manipulation of the argument path leads to deserialization. An attack has to be approached locally. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-5173?

3 open source packages ship an affected version, including label-studio-ml. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `label-studio-ml` | PyPI | All versions to 1.0.9 | None |
| `label-studio-ml` | PyPI | All versions to 1.0.9 | None |
| `label-studio-ml` | PyPI | All versions to 1.0.9 | None |

Products: Humansignal Label Studio Ml Backend.

## How do I fix CVE-2025-5173?

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

## Is CVE-2025-5173 being exploited?

There is no known exploitation of CVE-2025-5173 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5173 and fix it if it is affected.

What it is: CVE-2025-5173 is a medium-severity unsafe deserialization vulnerability in HumanSignal label-studio-ml-backend, published on 26 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5173 in the wild and no public exploit code.

Affected packages and fixed versions:
- label-studio-ml (PyPI): affected all versions up to 1.0.9; no fix listed
- label-studio-ml (PyPI): affected all versions up to 1.0.9; no fix listed
- label-studio-ml (PyPI): affected all versions up to 1.0.9; 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-2025-5173/ (Markdown: https://insights.sbomify.com/CVE-2025-5173/index.md)
```

## Sources

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

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