# CVE-2025-54955: Race condition in OpenNebula

> Unauthenticated attackers can exploit a race condition in FireEdge to steal valid JWTs and achieve full account takeover in OpenNebula.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Aug 2025
- **Updated:** 4 Aug 2025
- **Also known as:** GHSA-236c-586c-7q48, UBUNTU-CVE-2025-54955

## What is CVE-2025-54955?

CVE-2025-54955 is a high-severity vulnerability in OpenNebula, published on 2 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenNebula Community Edition (CE) before 7.0.0 and Enterprise Edition (EE) before 6.10.3 have a critical FireEdge race condition that can lead to full account takeover. By exploiting this, an unauthenticated attacker can obtain a valid JSON Web Token (JWT) belonging to a legitimate user without knowledge of their credentials.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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


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

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

## Is CVE-2025-54955 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54955 is a high-severity vulnerability in OpenNebula, published on 2 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54955 exists.

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

## Sources

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

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