{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32799 exists.","fix":"No fix has been published for CVE-2025-32799 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-32799 is a medium-severity path traversal vulnerability in conda-build, published on 16 Jun 2025. 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 CVE-2025-32799 and fix it if it is affected.\n\nWhat it is: CVE-2025-32799 is a medium-severity path traversal vulnerability in conda-build, published on 16 Jun 2025. An attacker can exploit it over the internet without logging in, 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-2025-32799 exists.\n\nAffected product: conda-build. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2025-32799/ (Markdown: https://insights.sbomify.com/CVE-2025-32799/index.md)","id":"CVE-2025-32799","markdown":"https://insights.sbomify.com/CVE-2025-32799/index.md","name":"CVE-2025-32799","record":{"aliases":["GHSA-h499-pxgj-qh5h"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Conda build tool","requires_auth":"none","summary":"Attackers can exploit path traversal in conda-build to overwrite arbitrary files, potentially leading to code execution or privilege escalation.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"conda-build","vendor":"anaconda"}],"cvss":{"score":5.6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Conda-build contains commands and tools to build conda packages. Prior to version 25.4.0, the conda-build processing logic is vulnerable to path traversal (Tarslip) attacks due to improper sanitization of tar entry paths. Attackers can craft tar archives containing entries with directory traversal sequences to write files outside the intended extraction directory. This could lead to arbitrary file overwrites, privilege escalation, or code execution if sensitive locations are targeted. This issue has been patched in version 25.4.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Conda-build Vulnerable to Path Traversal via Malicious Tar File","id":"CVE-2025-32799","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Supply chain in conda-build","id":"CVE-2025-32800"},"packages":[],"prev":{"headline":"Conda-build Allows Arbitrary Code Execution via Malicious Recipe Selectors","id":"CVE-2025-32798"},"products":["conda-build"],"published":"2025-06-16","related":[{"cvss_score":8.2,"headline":"Conda-build Allows Arbitrary Code Execution via Malicious Recipe Selectors","id":"CVE-2025-32798","kev_date_added":null,"published":"2025-06-16"},{"cvss_score":7.2,"headline":"Supply chain in conda-build","id":"CVE-2025-32800","kev_date_added":null,"published":"2025-06-16"},{"cvss_score":6,"headline":"Conda-build Insecure Build Script Permissions Enabling Arbitrary Code Execution","id":"CVE-2025-32797","kev_date_added":null,"published":"2025-06-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["conda"]},"summary":"Attackers can exploit path traversal in conda-build to overwrite arbitrary files, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2025-32799/"}