# CVE-2025-35471: conda-forge openssl-feedstock writable OPENSSLDIR

> Local attackers can execute arbitrary code by writing to the OpenSSL configuration directory due to insecure permissions on Windows.

- **Severity:** High 7.0 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 May 2025
- **Updated:** 22 May 2025
- **Also known as:** GHSA-wv5q-x2gm-xf7j

## What is CVE-2025-35471?

CVE-2025-35471 is a high-severity path traversal vulnerability in conda-forge miniforge, published on 13 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

conda-forge openssl-feedstock before 066e83c (2024-05-20), on Microsoft Windows, configures OpenSSL to use an OPENSSLDIR file path that can be written to by non-privilged local users. By writing a specially crafted openssl.cnf file in OPENSSLDIR, a non-privileged local user can execute arbitrary code with the privileges of the user or process loading openssl-feedstock DLLs. Miniforge before 24.5.0 is also affected.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 2 products.


Products: Conda-Forge Miniforge, Conda-Forge Openssl-Feedstock.

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

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

## Is CVE-2025-35471 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-35471 is a high-severity path traversal vulnerability in conda-forge miniforge, published on 13 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-35471 exists.

Affected product: conda-forge miniforge. 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-35471/ (Markdown: https://insights.sbomify.com/CVE-2025-35471/index.md)
```

## Sources

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

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