{"answers":{"affected":"2 open source packages ship an affected version, including uu_rm. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-35349 in the wild and no public exploit code.","fix":"Upgrade uu_rm to 0.7.0 or later.","what":"CVE-2026-35349 is a medium-severity path traversal vulnerability in Uutils coreutils, published on 22 Apr 2026. 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-2026-35349 and fix it if it is affected.\n\nWhat it is: CVE-2026-35349 is a medium-severity path traversal vulnerability in Uutils coreutils, published on 22 Apr 2026. 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-2026-35349 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- uu_rm (crates.io): affected all versions; fixed in 0.7.0\n- uu_rm (crates.io): affected all versions; fixed in 0.7.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-35349/ (Markdown: https://insights.sbomify.com/CVE-2026-35349/index.md)","id":"CVE-2026-35349","markdown":"https://insights.sbomify.com/CVE-2026-35349/index.md","name":"CVE-2026-35349","record":{"aliases":["DEBIAN-CVE-2026-35349","GHSA-7cr3-h577-g38j","UBUNTU-CVE-2026-35349"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"uutils coreutils","requires_auth":"none","summary":"Attackers can bypass rm's root protection via symlinks, causing accidental or malicious deletion of the entire root filesystem.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"canonical","cpe":[{"product":"coreutils","vendor":"uutils"}],"cvss":{"score":6.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"description":"A vulnerability in the rm utility of uutils coreutils allows a bypass of the --preserve-root protection. The implementation uses a path-string check rather than comparing device and inode numbers to identify the root directory. An attacker or accidental user can bypass this safeguard by using a symbolic link that resolves to the root directory (e.g., /tmp/rootlink -\u003e /), potentially leading to the unintended recursive deletion of the entire root filesystem.","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":"uutils coreutils Path-Based Safety Bypass with --preserve-root","id":"CVE-2026-35349","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"uutils coreutils cp Unexpected Privileged Executable Creation with -p","id":"CVE-2026-35350"},"packages":[{"ecosystem":"crates.io","fixed":["0.7.0"],"introduced":["0"],"last_affected":[],"package":"uu_rm","purl":null,"source":"GHSA-7cr3-h577-g38j"},{"ecosystem":"crates.io","fixed":["0.7.0"],"introduced":["0"],"last_affected":[],"package":"uu_rm","purl":"pkg:cargo/uu_rm","source":"GHSA-7cr3-h577-g38j"}],"prev":{"headline":"uutils coreutils sort Local Denial of Service via Forced UTF-8 Parsing","id":"CVE-2026-35348"},"products":["coreutils"],"published":"2026-04-22","related":[{"cvss_score":7.3,"headline":"uutils coreutils chmod Path Traversal Bypass of --preserve-root","id":"CVE-2026-35338","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":7.2,"headline":"uutils coreutils chroot Local Privilege Escalation and chroot Escape in via Name Service Switch (NSS) Injection","id":"CVE-2026-35368","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":7.1,"headline":"uutils coreutils mkfifo Unauthorized Permission Change on Existing Files","id":"CVE-2026-35341","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":7,"headline":"uutils coreutils mkfifo Privilege Escalation via TOCTOU Race Condition","id":"CVE-2026-35352","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":6.6,"headline":"uutils coreutils cp Unexpected Privileged Executable Creation with -p","id":"CVE-2026-35350","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":6.6,"headline":"uutils coreutils mv Denial of Service and Data Duplication via Improper Symlink Expansion","id":"CVE-2026-35365","kev_date_added":null,"published":"2026-04-22"}],"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":"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-04-22","vendors":["Uutils"]},"summary":"Attackers can bypass rm's root protection via symlinks, causing accidental or malicious deletion of the entire root filesystem.","url":"https://insights.sbomify.com/CVE-2026-35349/"}