Skip to main content
VulnerabilityPublished

CVE-2025-66432: In Oxide control plane 15 through 17 before 17.1, API tokens can be renewed past their expiration date

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-66432· Medium 5.0

Not known to be exploited · CVSS 5.0 Medium.

Data as of 20 Nov 2026, 00:55 UTC

CVSS 3.1 base score
5.0Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (mitre)CVSS 3.15.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHuboxidecomputer/omicronpkg:github/oxidecomputer/omicronOther threatsAffected
  • =15
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, organizations should monitor API token usage and consider implementing additional controls around token renewal processes.

Description

A vulnerability in Oxide control plane versions 15 through 17 before 17.1 allows API tokens to be renewed beyond their intended expiration date. This flaw could enable attackers with limited privileges to extend the validity of API tokens, potentially increasing the window for unauthorized actions. The issue is tracked as CVE-2025-66432 and has a medium severity rating.

References

Community reviews

Loading reviews…