{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49598 exists.","fix":"No fix has been published for CVE-2025-49598 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-49598 is a medium-severity code injection vulnerability in conda-forge-ci-setup-feedstock, published on 13 Jun 2025. 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-2025-49598 and fix it if it is affected.\n\nWhat it is: CVE-2025-49598 is a medium-severity code injection vulnerability in conda-forge-ci-setup-feedstock, published on 13 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49598 exists.\n\nAffected product: conda-forge-ci-setup-feedstock. 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-49598/ (Markdown: https://insights.sbomify.com/CVE-2025-49598/index.md)","id":"CVE-2025-49598","markdown":"https://insights.sbomify.com/CVE-2025-49598/index.md","name":"CVE-2025-49598","record":{"aliases":["GHSA-jh2q-mrmj-hff3"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"CI/CD build tool","requires_auth":"low_privilege","summary":"An attacker can execute arbitrary code by injecting malicious payloads into meta.yaml files processed by conda-forge-ci-setup during CI builds.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-95","name":"Improper Neutralization of Directives in Dynamically Evaluated Code"}],"description":"conda-forge-ci-setup is a package installed by conda-forge each time a build is run on CI. The conda-forge-ci-setup-feedstock setup script is vulnerable due to the unsafe use of the eval function when parsing version information from a custom-formatted meta.yaml file. An attacker controlling meta.yaml can inject malicious code into the version assignment, which is executed during file processing, leading to arbitrary code execution. Exploitation requires an attacker to modify the recipe file by manipulating the RECIPE_DIR variable and introducing a malicious meta.yaml file. While this is more feasible in CI/CD pipelines, it is uncommon in typical environments, reducing overall risk. This vulnerability is fixed in 4.15.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-forge-ci-setup Allows Arbitrary Code Execution via Insecure Version Parsing","id":"CVE-2025-49598","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in EG8141A5","id":"CVE-2025-49599"},"packages":[],"prev":{"headline":"handcraftedinthealps goodby-csv Potential Gadget Chain allowing Remote Code Execution","id":"CVE-2025-49597"},"products":["conda-forge-ci-setup-feedstock"],"published":"2025-06-13","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2025-06-13","vendors":["conda-forge"]},"summary":"An attacker can execute arbitrary code by injecting malicious payloads into meta.yaml files processed by conda-forge-ci-setup during CI builds.","url":"https://insights.sbomify.com/CVE-2025-49598/"}