{"answers":{"affected":"3 open source packages ship an affected version, including astral-tokio-tar.","exploited":"There is no known exploitation of GHSA-xx64-wwv2-hcqq in the wild and no public exploit code.","fix":"Upgrade astral-tokio-tar to 0.6.1 or later.","what":"GHSA-xx64-wwv2-hcqq is a path traversal vulnerability in astral-tokio-tar, published on 27 Apr 2026. 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 GHSA-xx64-wwv2-hcqq and fix it if it is affected.\n\nWhat it is: GHSA-xx64-wwv2-hcqq is a path traversal vulnerability in astral-tokio-tar, published on 27 Apr 2026. 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: There is no known exploitation of GHSA-xx64-wwv2-hcqq 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.6.1\n- astral-tokio-tar (crates.io): affected all versions; fixed in 0.6.1\n- astral-tokio-tar (crates.io): affected from 0.0.0-0; fixed in 0.6.1\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/GHSA-xx64-wwv2-hcqq/ (Markdown: https://insights.sbomify.com/GHSA-xx64-wwv2-hcqq/index.md)","id":"GHSA-xx64-wwv2-hcqq","markdown":"https://insights.sbomify.com/GHSA-xx64-wwv2-hcqq/index.md","name":"GHSA-xx64-wwv2-hcqq","record":{"aliases":["RUSTSEC-2026-0113"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust tar library","requires_auth":"none","summary":"An attacker can craft a tar archive to change permissions of arbitrary directories outside the extraction path via symlink traversal.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n\nIn versions 0.6.0 and earlier of astral-tokio-tar, the `unpack_in` API could inadvertently modify the permissions of external (i.e. non-archive) directories outside of the archive. An attacker could use this to contrite a tar archive that maliciously changes directory permissions outside of its intended hierarchy. This flaw only affects directories; individual file permissions cannot be modified via it.\n\nSee GHSA-j4xf-2g29-59ph for the equivalent flaw in the `tar` crate.\n\n### Patches\n\nVersions 0.6.1 and newer of astral-tokio-tar use `fs::symlink_metdata` rather than `fs::metadata`, avoiding the traversal. \n\n### Workarounds\n\nUsers are advised to upgrade to version 0.6.1 or newer to address this advisory.\n\nUsers should experience no breaking changes as a result of the patch above.\n\n### Resources\n\n- GHSA-j4xf-2g29-59ph for the original `tar` vulnerability\n\n### Attribution\n\n- Reporter: Adam Harvey (@lawngnome)","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"astral-tokio-tar: `unpack_in` can chmod arbitrary directories by following symlinks","id":"GHSA-xx64-wwv2-hcqq","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0"],"last_affected":[],"package":"astral-tokio-tar","purl":null,"source":"GHSA-xx64-wwv2-hcqq"},{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0"],"last_affected":[],"package":"astral-tokio-tar","purl":"pkg:cargo/astral-tokio-tar","source":"GHSA-xx64-wwv2-hcqq"},{"ecosystem":"crates.io","fixed":["0.6.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"astral-tokio-tar","purl":"pkg:cargo/astral-tokio-tar","source":"RUSTSEC-2026-0113"}],"products":null,"published":"2026-04-27","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker can craft a tar archive to change permissions of arbitrary directories outside the extraction path via symlink traversal.","url":"https://insights.sbomify.com/GHSA-xx64-wwv2-hcqq/"}