# CVE-2025-59378: Privilege escalation in Guix

> A local attacker can create a setuid program via content-addressed mirrors to gain build user privileges in GNU Guix.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2025
- **Updated:** 15 Sep 2025
- **Also known as:** DEBIAN-CVE-2025-59378, GHSA-75hx-v6j6-m6h7, UBUNTU-CVE-2025-59378

## What is CVE-2025-59378?

CVE-2025-59378 is a medium-severity vulnerability in GNU Guix, published on 15 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In guix-daemon in GNU Guix before 1618ca7, a content-addressed-mirrors file can be written to create a setuid program that allows a regular user to gain the privileges of the build user that runs it (even after the build has ended).

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

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


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

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

## Is CVE-2025-59378 being exploited?

There is no known exploitation of CVE-2025-59378 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59378 is a medium-severity vulnerability in GNU Guix, published on 15 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59378 in the wild and no public exploit code.

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

## Sources

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

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