# CVE-2025-46415: Race condition in Nix

> A race condition in Nix, Lix, and Guix allows attackers to remove content from arbitrary folders, requiring an upgrade to patched versions.

- **Severity:** Low 3.2 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jun 2025
- **Updated:** 27 Jun 2025
- **Also known as:** DEBIAN-CVE-2025-46415, GHSA-r756-7c6v-6jh7, UBUNTU-CVE-2025-46415

## What is CVE-2025-46415?

CVE-2025-46415 is a low-severity vulnerability in NixOS Nix, published on 27 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A race condition in the Nix, Lix, and Guix package managers allows the removal of content from arbitrary folders. This affects Nix before 2.24.15, 2.26.4, 2.28.4, and 2.29.1; Lix before 2.91.2, 2.92.2, and 2.93.1; and Guix before 1.4.0-38.0e79d5b.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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


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

Upgrade to a fixed version.

## Is CVE-2025-46415 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46415 is a low-severity vulnerability in NixOS Nix, published on 27 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-46415 exists.

Affected product: NixOS Nix. 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-46415/ (Markdown: https://insights.sbomify.com/CVE-2025-46415/index.md)
```

## Sources

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

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