{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-32800 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-32800 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-32800 is a high-severity vulnerability in conda-build, published on 16 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-32800 and fix it if it is affected.\n\nWhat it is: CVE-2025-32800 is a high-severity vulnerability in conda-build, published on 16 Jun 2025. 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-2025-32800 in the wild and no public exploit code.\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-32800/ (Markdown: https://insights.sbomify.com/CVE-2025-32800/index.md)","id":"CVE-2025-32800","markdown":"https://insights.sbomify.com/CVE-2025-32800/index.md","name":"CVE-2025-32800","record":{"aliases":["GHSA-83gh-p93g-cwgx"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Conda build tool","requires_auth":"none","summary":"Attackers can hijack a missing dependency namespace to inject malicious code during package installation, affecting developers using Conda-build.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"conda-build","vendor":"anaconda"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-1357","name":"Reliance on Insufficiently Trustworthy Component"}],"description":"Conda-build contains commands and tools to build conda packages. Prior to version 25.3.0, the pyproject.toml lists conda-index as a Python dependency. This package is not published in PyPI. An attacker could claim this namespace and upload arbitrary (malicious) code to the package, and then exploit pip install commands by injecting the malicious dependency in the solve. This issue has been fixed in version 25.3.0. A workaround involves using --no-deps for pip install-ing the project from the repository.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Supply chain in conda-build","id":"CVE-2025-32800","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Loading a malicious hook library can lead to local privilege escalation","id":"CVE-2025-32801"},"packages":[],"prev":{"headline":"Conda-build Vulnerable to Path Traversal via Malicious Tar File","id":"CVE-2025-32799"},"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":6,"headline":"Conda-build Insecure Build Script Permissions Enabling Arbitrary Code Execution","id":"CVE-2025-32797","kev_date_added":null,"published":"2025-06-16"},{"cvss_score":5.6,"headline":"Conda-build Vulnerable to Path Traversal via Malicious Tar File","id":"CVE-2025-32799","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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["conda"]},"summary":"Attackers can hijack a missing dependency namespace to inject malicious code during package installation, affecting developers using Conda-build.","url":"https://insights.sbomify.com/CVE-2025-32800/"}