HumanSignal label-studio-ml-backend Deserialization of Untrusted Data vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2025-5173: 0.24% estimated exploitation activity in the next 30 days; percentile 15.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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/labelstudioml/examples/yolo/utils/neuralnets.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.

Published by the source

26 May 2025, 09:30 UTC

Last modified by the source

7 Jul 2026, 17:57 UTC

Source last checked

26 Oct 2026, 13:32 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-55g9-6c2x-gf8q

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-55g9-6c2x-gf8q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-5173

Advisory: HumanSignal label-studio-ml-backend Deserialization of Untrusted Data vulnerability
IDs: CVE-2025-5173, GHSA-55g9-6c2x-gf8q
Record: https://patchnext.com/advisories/cve-2025-5173 (revision 3, source checked 26 Oct 2026, 13:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI label-studio-ml: affected <= 1.0.9

## Suggested inspection (read-only)
- `python -m pip show label-studio-ml`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on label-studio-ml.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-55g9-6c2x-gf8q (OSV record GHSA-55g9-6c2x-gf8q lists affected ranges: PyPI label-studio-ml >=0 <=1.0.9)
- Verified: https://github.com/advisories/GHSA-55g9-6c2x-gf8q (GitHub-reviewed advisory GHSA-55g9-6c2x-gf8q lists affected ranges: PyPI label-studio-ml >=0 <=1.0.9)

Commands are suggestions: review each one before running it.