{"answers":{"affected":"3 open source packages ship an affected version, including proot-distro.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54574 exists.","fix":"Upgrade proot-distro to 5.1.5 or later.","what":"CVE-2026-54574 is a high-severity path traversal vulnerability in termux proot-distro, published on 29 Jul 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 CVE-2026-54574 and fix it if it is affected.\n\nWhat it is: CVE-2026-54574 is a high-severity path traversal vulnerability in termux proot-distro, published on 29 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54574 exists.\n\nAffected packages and fixed versions:\n- proot-distro (PyPI): affected all versions; fixed in 5.1.5\n- proot-distro (PyPI): affected all versions; fixed in 5.1.5\n- proot-distro (PyPI): affected all versions; fixed in 5.1.5\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-54574/ (Markdown: https://insights.sbomify.com/CVE-2026-54574/index.md)","id":"CVE-2026-54574","markdown":"https://insights.sbomify.com/CVE-2026-54574/index.md","name":"CVE-2026-54574","record":{"aliases":["GHSA-9xq3-3fqg-4vg7","PYSEC-2026-3608"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"proot-distro utility","requires_auth":"none","summary":"A malicious tar archive can exploit symlink handling in proot-distro to write arbitrary files to the host filesystem, potentially leading to code execution.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-61","name":"UNIX Symbolic Link (Symlink) Following"}],"description":"proot-distro is a utility for managing proot containers. Prior to version 5.1.5, proot-distro install extracted plain tarball root filesystems through _extract_plain_tar() in proot_distro/commands/install.py and Docker layers through _apply_layer() in proot_distro/helpers/docker.py without validating archive-controlled symlink targets in member.linkname, allowing a malicious archive to plant an absolute host-path symlink and write files through it onto the host filesystem. This issue is fixed in version 5.1.5.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"`proot-distro install` has a Symlink Escape (Arbitrary Host File Write) via Malicious Tar Archive","id":"CVE-2026-54574","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"mport package fetch and clean paths are vulnerable to TOCTOU filesystem races","id":"CVE-2026-54575"},"packages":[{"ecosystem":"PyPI","fixed":["5.1.5"],"introduced":["0"],"last_affected":[],"package":"proot-distro","purl":null,"source":"GHSA-9xq3-3fqg-4vg7"},{"ecosystem":"PyPI","fixed":["5.1.5"],"introduced":["0"],"last_affected":[],"package":"proot-distro","purl":"pkg:pypi/proot-distro","source":"GHSA-9xq3-3fqg-4vg7"},{"ecosystem":"PyPI","fixed":["5.1.5"],"introduced":["0"],"last_affected":[],"package":"proot-distro","purl":"pkg:pypi/proot-distro","source":"PYSEC-2026-3608"}],"prev":{"headline":"Authorization Bypass in API Key/OAuth Scopes via Path Parsing Discrepancy","id":"CVE-2026-54573"},"products":["proot-distro"],"published":"2026-07-29","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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-29","vendors":["termux"]},"summary":"A malicious tar archive can exploit symlink handling in proot-distro to write arbitrary files to the host filesystem, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2026-54574/"}