{"answers":{"affected":"2 open source packages ship an affected version, including astral-tokio-tar.","exploited":"There is no known exploitation of CVE-2025-59825 in the wild and no public exploit code.","fix":"Upgrade astral-tokio-tar to 0.5.4 or later.","what":"CVE-2025-59825 is a medium-severity path traversal vulnerability in astral-sh tokio-tar, published on 23 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-59825 and fix it if it is affected.\n\nWhat it is: CVE-2025-59825 is a medium-severity path traversal vulnerability in astral-sh tokio-tar, published on 23 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-59825 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- astral-tokio-tar (crates.io): affected all versions; fixed in 0.5.4\n- astral-tokio-tar (crates.io): affected all versions; fixed in 0.5.4\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-59825/ (Markdown: https://insights.sbomify.com/CVE-2025-59825/index.md)","id":"CVE-2025-59825","markdown":"https://insights.sbomify.com/CVE-2025-59825/index.md","name":"CVE-2025-59825","record":{"aliases":["DEBIAN-CVE-2025-59825","GHSA-3wgq-wrwc-vqmv","UBUNTU-CVE-2025-59825"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust tar library","requires_auth":"none","summary":"Attackers can exploit path traversal in astral-tokio-tar to write arbitrary files outside the destination directory, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-61","name":"UNIX Symbolic Link (Symlink) Following"},{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"astral-tokio-tar is a tar archive reading/writing library for async Rust. In versions 0.5.3 and earlier of astral-tokio-tar, tar archives may extract outside of their intended destination directory when using the Entry::unpack_in_raw API. Additionally, the Entry::allow_external_symlinks control (which defaults to true) could be bypassed via a pair of symlinks that individually point within the destination but combine to point outside of it. These behaviors could be used individually or combined to bypass the intended security control of limiting extraction to the given directory. This in turn would allow an attacker with a malicious tar archive to perform an arbitrary file write and potentially pivot into code execution. This issue has been patched in version 0.5.4. There is no workaround other than upgrading.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"astral-tokio-tar has a path traversal in tar extraction","id":"CVE-2025-59825","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"FlagForgeCTF Vulnerable to Unauthorized Problem Creation","id":"CVE-2025-59826"},"packages":[{"ecosystem":"crates.io","fixed":["0.5.4"],"introduced":["0"],"last_affected":[],"package":"astral-tokio-tar","purl":null,"source":"GHSA-3wgq-wrwc-vqmv"},{"ecosystem":"crates.io","fixed":["0.5.4"],"introduced":["0"],"last_affected":[],"package":"astral-tokio-tar","purl":"pkg:cargo/astral-tokio-tar","source":"GHSA-3wgq-wrwc-vqmv"}],"prev":{"headline":"Omni Wireguard SideroLink potential escape","id":"CVE-2025-59824"},"products":["tokio-tar"],"published":"2025-09-23","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-24","vendors":["astral-sh"]},"summary":"Attackers can exploit path traversal in astral-tokio-tar to write arbitrary files outside the destination directory, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2025-59825/"}