# CVE-2025-66432: Business logic in Omicron

> Attackers can renew expired API tokens in Oxide control plane, bypassing expiration controls and maintaining unauthorized access.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Nov 2025
- **Updated:** 1 Dec 2025
- **Also known as:** GHSA-xg9f-qgvm-j933

## What is CVE-2025-66432?

CVE-2025-66432 is a medium-severity vulnerability in Oxide Omicron, published on 30 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Oxide control plane 15 through 17 before 17.1, API tokens can be renewed past their expiration date.

Weakness: CWE-420 (Unprotected Alternate Channel)

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


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

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

## Is CVE-2025-66432 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66432 is a medium-severity vulnerability in Oxide Omicron, published on 30 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-66432 in the wild and no public exploit code.

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

## Sources

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

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