{"answers":{"affected":"1 open source package ship an affected version, including decompress.","exploited":"There is no known exploitation of RUSTSEC-2026-0328 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2026-0328 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2026-0328 is a path traversal vulnerability in decompress, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0328 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0328 is a path traversal vulnerability in decompress, published on 19 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of RUSTSEC-2026-0328 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- decompress (crates.io): affected from 0.0.0-0; no fix listed\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/RUSTSEC-2026-0328/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0328/index.md)","id":"RUSTSEC-2026-0328","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0328/index.md","name":"RUSTSEC-2026-0328","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust decompression library","requires_auth":"none","summary":"A malicious tar archive can write files outside the destination directory, potentially leading to arbitrary file overwrite or code execution.","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":"The tar-family extractors in `decompress` (`.tar`, `.tar.gz`, `.tar.xz`,\n`.tar.bz2`, `.tar.zst`) build each output path from the **raw archive entry path**\nand write to it with no traversal check, so a malicious archive can write files\n**outside** the destination directory, a \"tar-slip\" / zip-slip path traversal\n(CWE-22 / CWE-23).\n\nIn `src/decompressors/tar_common.rs` (`tar_extract`):\n\n```rust\nlet filepath = entry.path()?;                                    // raw entry path\nlet filepath = filepath.components().skip(opts.strip).collect::\u003cPathBuf\u003e();\n                                     // strips leading components only — keeps `..`\nlet outpath = to.join(filepath);\n// ...\nlet mut outfile = fs::File::create(\u0026outpath)?;                   // writes anywhere\n```\n\n`.components().skip(opts.strip)` removes a fixed number of *leading* path\ncomponents but leaves interior `..` components intact so an entry named \ne.g. `../../../../home/\u003cuser\u003e/.bashrc`, or an absolute path, resolves **outside** \n`to`. This affects all platforms.","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":false,"headline":"`decompress`: tar-family extractors write archive entries without a path-traversal check (tar-slip)","id":"RUSTSEC-2026-0328","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"decompress","purl":"pkg:cargo/decompress","source":"RUSTSEC-2026-0328"}],"products":null,"published":"2026-09-19","related":[],"sources":[{"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":"A malicious tar archive can write files outside the destination directory, potentially leading to arbitrary file overwrite or code execution.","url":"https://insights.sbomify.com/RUSTSEC-2026-0328/"}