# CVE-2025-49598: conda-forge-ci-setup Allows Arbitrary Code Execution via Insecure Version Parsing

> An attacker can execute arbitrary code by injecting malicious payloads into meta.yaml files processed by conda-forge-ci-setup during CI builds.

- **Severity:** Medium 4.4 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2025
- **Updated:** 13 Jun 2025
- **Also known as:** GHSA-jh2q-mrmj-hff3

## What is CVE-2025-49598?

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.

### Official 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.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code)

## Which versions are affected by CVE-2025-49598?


## How do I fix CVE-2025-49598?

No fix has been published for CVE-2025-49598 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-49598 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49598 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-49598 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-49598 exists.

Affected product: conda-forge-ci-setup-feedstock. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-49598/ (Markdown: https://insights.sbomify.com/CVE-2025-49598/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-49598
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-49598
- OSV: https://osv.dev/vulnerability/CVE-2025-49598

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-49598/
Summaries are generated and may contain mistakes; the official description above is the record.