{"answers":{"affected":"3 open source packages ship an affected version, including astral-tokio-tar. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-32766 in the wild and no public exploit code.","fix":"Upgrade astral-tokio-tar to 0.6.0 or later.","what":"CVE-2026-32766 is a low-severity vulnerability in astral-sh tokio-tar, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-32766 and fix it if it is affected.\n\nWhat it is: CVE-2026-32766 is a low-severity vulnerability in astral-sh tokio-tar, published on 20 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-32766 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.0\n- astral-tokio-tar (crates.io): affected all versions; fixed in 0.6.0\n- astral-tokio-tar (crates.io): affected from 0.0.0-0; fixed in 0.6.0\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-2026-32766/ (Markdown: https://insights.sbomify.com/CVE-2026-32766/index.md)","id":"CVE-2026-32766","markdown":"https://insights.sbomify.com/CVE-2026-32766/index.md","name":"CVE-2026-32766","record":{"aliases":["DEBIAN-CVE-2026-32766","GHSA-6gx3-4362-rf54","MINI-5fm9-6g6x-ccmr","RUSTSEC-2026-0066","UBUNTU-CVE-2026-32766"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust tar library","requires_auth":"none","summary":"Malformed PAX extensions are silently skipped, potentially enabling parser differential attacks if combined with a vulnerable secondary parser.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"astral-tokio-tar","vendor":"astral"}],"cvss":{"score":1.7,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-436","name":"Interpretation Conflict"}],"description":"astral-tokio-tar is a tar archive reading/writing library for async Rust. In versions 0.5.6 and earlier, malformed PAX extensions were silently skipped when parsing tar archives. This silent skipping (rather than rejection) of invalid PAX extensions could be used as a building block for a parser differential, for example by silently skipping a malformed GNU “long link” extension so that a subsequent parser would misinterpret the extension. In practice, exploiting this behavior in astral-tokio-tar requires a secondary misbehaving tar parser, i.e. one that insufficiently validates malformed PAX extensions and interprets them rather than skipping or erroring on them. This vulnerability is considered low-severity as it requires a separate vulnerability against any unrelated tar parser. This issue has been fixed in version 0.6.0.","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 insufficiently validates PAX extensions during extraction","id":"CVE-2026-32766","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"other","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"SiYuan: Authorization Bypass Allows Arbitrary SQL Execution via Search API","id":"CVE-2026-32767"},"packages":[{"ecosystem":"crates.io","fixed":["0.6.0"],"introduced":["0"],"last_affected":[],"package":"astral-tokio-tar","purl":null,"source":"GHSA-6gx3-4362-rf54"},{"ecosystem":"crates.io","fixed":["0.6.0"],"introduced":["0"],"last_affected":[],"package":"astral-tokio-tar","purl":"pkg:cargo/astral-tokio-tar","source":"GHSA-6gx3-4362-rf54"},{"ecosystem":"crates.io","fixed":["0.6.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"astral-tokio-tar","purl":"pkg:cargo/astral-tokio-tar","source":"RUSTSEC-2026-0066"}],"prev":{"headline":"This repository is no longer public.","id":"CVE-2026-32765"},"products":["tokio-tar"],"published":"2026-03-20","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":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"2026-03-20","vendors":["astral-sh"]},"summary":"Malformed PAX extensions are silently skipped, potentially enabling parser differential attacks if combined with a vulnerable secondary parser.","url":"https://insights.sbomify.com/CVE-2026-32766/"}