Label Studio has a Path Traversal Vulnerability via image Field
CVE-2025-25295GHSA-rgv9-w7jp-m23g
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (label-studio-sdk 1.0.10), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI label-studio-sdk
- Affected
- < 1.0.10
- Fixed in
- 1.0.10
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-rgv9-w7jp-m23g lists affected ranges: PyPI label-studio-sdk >=0 <1.0.10 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-rgv9-w7jp-m23g lists affected ranges: PyPI label-studio-sdk >=0 <1.0.10
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2025-25295: 0.76% estimated exploitation activity in the next 30 days; percentile 55.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Description A path traversal vulnerability in Label Studio SDK versions prior to 1.0.10 allows unauthorized file access outside the intended directory structure. Label Studio versions before 1.16.0 specified SDK versions prior to 1.0.10 as dependencies, and the issue was confirmed in Label Studio version 1.13.2.dev0; therefore, Label Studio users should upgrade to 1.16.0 or newer to mitigate it. The flaw exists in the VOC, COCO and YOLO export functionalites. These functions invoke a download function on the label-studio-sdk python package, which fails to validate file paths when processing image references during task exports: By creating tasks with path traversal sequences in the image field, an attacker can force the application to read files from arbitrary server filesystem locations when exporting projects in any of the mentioned formats. Note that there are two different possible code paths leading to this result, one for the isuploadedfile and another one for the islocalfile.…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-rgv9-w7jp-m23g
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-rgv9-w7jp-m23g
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-25295 Advisory: Label Studio has a Path Traversal Vulnerability via image Field IDs: CVE-2025-25295, GHSA-rgv9-w7jp-m23g Record: https://patchnext.com/advisories/cve-2025-25295 (revision 3, source checked 26 Oct 2026, 13:31 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: label-studio-sdk 1.0.10. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI label-studio-sdk: affected < 1.0.10; fixed in 1.0.10 ## Suggested inspection (read-only) - `python -m pip show label-studio-sdk`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on label-studio-sdk. - 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-rgv9-w7jp-m23g (OSV record GHSA-rgv9-w7jp-m23g lists affected ranges: PyPI label-studio-sdk >=0 <1.0.10 (fixed)) - Verified: https://github.com/advisories/GHSA-rgv9-w7jp-m23g (GitHub-reviewed advisory GHSA-rgv9-w7jp-m23g lists affected ranges: PyPI label-studio-sdk >=0 <1.0.10) Commands are suggestions: review each one before running it.
Loading voting…