# CVE-2025-3931: Yggdrasil: local privilege escalation in yggdrasil

> Local attackers can exploit missing authentication in Yggdrasil DBus methods to install arbitrary RPM packages, leading to privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** Yes
- **Published:** 14 May 2025
- **Updated:** 11 Nov 2025
- **Also known as:** GHSA-rpg2-jvhp-h354, GO-2025-3688

## What is CVE-2025-3931?

CVE-2025-3931 is a high-severity missing authorization vulnerability in Red Hat Enterprise Linux 10, published on 14 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in Yggdrasil, which acts as a system broker, allowing the processes to communicate to other children's "worker" processes through the DBus component. Yggdrasil creates a DBus method to dispatch messages to workers. However, it misses authentication and authorization checks, allowing every system user to call it. One available Yggdrasil worker acts as a package manager with capabilities to create and enable new repositories and install or remove packages. 

This flaw allows an attacker with access to the system to leverage the lack of authentication on the dispatch message to force the Yggdrasil worker to install arbitrary RPM packages. This issue results in local privilege escalation, enabling the attacker to access and modify sensitive system data.

Weakness: CWE-280 (Improper Handling of Insufficient Permissions or Privileges)

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

3 open source packages ship an affected version, including github.com/redhatinsights/yggdrasil.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/redhatinsights/yggdrasil` | Go | All versions | None |
| `github.com/redhatinsights/yggdrasil` | Go | All versions to 0.4.6 | None |
| `github.com/redhatinsights/yggdrasil` | Go | All versions to 0.4.6 | None |

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

Apply the vendor's patch.

## Is CVE-2025-3931 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3931 is a high-severity missing authorization vulnerability in Red Hat Enterprise Linux 10, published on 14 May 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-3931 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/redhatinsights/yggdrasil (Go): affected all versions; no fix listed
- github.com/redhatinsights/yggdrasil (Go): affected all versions up to 0.4.6; no fix listed
- github.com/redhatinsights/yggdrasil (Go): affected all versions up to 0.4.6; no fix listed

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-3931/ (Markdown: https://insights.sbomify.com/CVE-2025-3931/index.md)
```

## Sources

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

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