{"answers":{"affected":"3 open source packages ship an affected version, including clearml.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8917 exists.","fix":"Upgrade clearml to 2.0.2 or later.","what":"CVE-2025-8917 is a medium-severity path traversal vulnerability in allegroai/clearml, published on 5 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-8917 and fix it if it is affected.\n\nWhat it is: CVE-2025-8917 is a medium-severity path traversal vulnerability in allegroai/clearml, published on 5 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-8917 exists.\n\nAffected packages and fixed versions:\n- clearml (PyPI): affected all versions; fixed in 2.0.2\n- clearml (PyPI): affected all versions; fixed in 2.0.2\n- clearml (PyPI): affected all versions; fixed in 2.0.2\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-8917/ (Markdown: https://insights.sbomify.com/CVE-2025-8917/index.md)","id":"CVE-2025-8917","markdown":"https://insights.sbomify.com/CVE-2025-8917/index.md","name":"CVE-2025-8917","record":{"aliases":["GHSA-579p-qf78-fqm2","PYSEC-2026-1255"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python machine learning library","requires_auth":"high_privilege","summary":"Path traversal in allegroai/clearml allows arbitrary file writes via symlink handling, potentially leading to remote code execution.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"A vulnerability in allegroai/clearml version v2.0.1 allows for path traversal due to improper handling of symbolic and hard links in the `safe_extract` function. This flaw can lead to arbitrary file writes outside the intended directory, potentially resulting in remote code execution if critical files are overwritten.","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":"Path Traversal Leading to Remote Code Execution in allegroai/clearml","id":"CVE-2025-8917","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":"Portabilis i-Educar Editar educar_instituicao_cad.php cross site scripting","id":"CVE-2025-8918"},"packages":[{"ecosystem":"PyPI","fixed":["2.0.2"],"introduced":["0"],"last_affected":[],"package":"clearml","purl":null,"source":"GHSA-579p-qf78-fqm2"},{"ecosystem":"PyPI","fixed":["2.0.2"],"introduced":["0"],"last_affected":[],"package":"clearml","purl":"pkg:pypi/clearml","source":"GHSA-579p-qf78-fqm2"},{"ecosystem":"PyPI","fixed":["2.0.2"],"introduced":["0"],"last_affected":[],"package":"clearml","purl":"pkg:pypi/clearml","source":"PYSEC-2026-1255"}],"prev":{"headline":"Possible DOS in processing large name constraint structures in PKIXCertPathReveiwer","id":"CVE-2025-8916"},"products":["allegroai/clearml"],"published":"2025-10-05","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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-06","vendors":["allegroai"]},"summary":"Path traversal in allegroai/clearml allows arbitrary file writes via symlink handling, potentially leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2025-8917/"}