# CVE-2025-25295: Label Studio has a Path Traversal Vulnerability via image Field > Authenticated attackers can read arbitrary server files via path traversal in image fields during project exports, exposing sensitive data. - **Severity:** High 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`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 Feb 2025 - **Updated:** 3 Mar 2025 - **Also known as:** GHSA-rgv9-w7jp-m23g, PYSEC-2026-1506 ## What is CVE-2025-25295? CVE-2025-25295 is a high-severity path traversal vulnerability in HumanSignal label-studio, published on 14 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Label Studio is an open source data labeling tool. A path traversal vulnerability in Label Studio SDK versions prior to 1.0.10 allows unauthorized file access outside the intended directory structure. The flaw exists in the VOC, COCO and YOLO export functionalities. 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. This is authentication-required vulnerability allowing arbitrary file reads from the server filesystem. It may lead to potential exposure of sensitive information like configuration files, credentials, and confidential data. 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. Weakness: CWE-26 (Path Traversal: '/dir/../filename'), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2025-25295? 3 open source packages ship an affected version, including label-studio-sdk. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `label-studio-sdk` | PyPI | All versions | 1.0.10 | | `label-studio-sdk` | PyPI | All versions | 1.0.10 | | `label-studio-sdk` | PyPI | All versions | 1.0.10 | ## How do I fix CVE-2025-25295? Upgrade label-studio-sdk to 1.0.10 or later. ## Is CVE-2025-25295 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25295 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-25295 and fix it if it is affected. What it is: CVE-2025-25295 is a high-severity path traversal vulnerability in HumanSignal label-studio, published on 14 Feb 2025. 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-2025-25295 exists. Affected packages and fixed versions: - label-studio-sdk (PyPI): affected all versions; fixed in 1.0.10 - label-studio-sdk (PyPI): affected all versions; fixed in 1.0.10 - label-studio-sdk (PyPI): affected all versions; fixed in 1.0.10 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-25295/ (Markdown: https://insights.sbomify.com/CVE-2025-25295/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-25295 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-25295 - OSV: https://osv.dev/vulnerability/CVE-2025-25295 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-25295/ Summaries are generated and may contain mistakes; the official description above is the record.