{"answers":{"affected":"3 open source packages ship an affected version, including label-studio-sdk.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25295 exists.","fix":"Upgrade label-studio-sdk to 1.0.10 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-25295 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25295 exists.\n\nAffected packages and fixed versions:\n- label-studio-sdk (PyPI): affected all versions; fixed in 1.0.10\n- label-studio-sdk (PyPI): affected all versions; fixed in 1.0.10\n- label-studio-sdk (PyPI): affected all versions; fixed in 1.0.10\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-25295/ (Markdown: https://insights.sbomify.com/CVE-2025-25295/index.md)","id":"CVE-2025-25295","markdown":"https://insights.sbomify.com/CVE-2025-25295/index.md","name":"CVE-2025-25295","record":{"aliases":["GHSA-rgv9-w7jp-m23g","PYSEC-2026-1506"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Data labeling tool","requires_auth":"none","summary":"Authenticated attackers can read arbitrary server files via path traversal in image fields during project exports, exposing sensitive data.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-26","name":"Path Traversal: '/dir/../filename'"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Label Studio has a Path Traversal Vulnerability via image Field","id":"CVE-2025-25295","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"Label Studio allows Cross-Site Scripting (XSS) via GET request to `/projects/upload-example` endpoint","id":"CVE-2025-25296"},"packages":[{"ecosystem":"PyPI","fixed":["1.0.10"],"introduced":["0"],"last_affected":[],"package":"label-studio-sdk","purl":null,"source":"GHSA-rgv9-w7jp-m23g"},{"ecosystem":"PyPI","fixed":["1.0.10"],"introduced":["0"],"last_affected":[],"package":"label-studio-sdk","purl":"pkg:pypi/label-studio-sdk","source":"GHSA-rgv9-w7jp-m23g"},{"ecosystem":"PyPI","fixed":["1.0.10"],"introduced":["0"],"last_affected":[],"package":"label-studio-sdk","purl":"pkg:pypi/label-studio-sdk","source":"PYSEC-2026-1506"}],"prev":{"headline":"Envoy Gateway Log Injection Vulnerability","id":"CVE-2025-25294"},"products":["label-studio"],"published":"2025-02-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-03","vendors":["HumanSignal"]},"summary":"Authenticated attackers can read arbitrary server files via path traversal in image fields during project exports, exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2025-25295/"}