CVE-2025-66432VulnerabilityPublished 30 Nov 2025Updated 1 Dec 2025

CVE-2025-66432: Oxide Omicron · Unprotected Alternate Channel

Affects Oxide OmicronSource CVE Database V5

Not known to be exploited · CVSS 5.0 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHuboxidecomputer/omicron`pkg:github/oxidecomputer/omicron`Other threats	Affected =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

1. Monitor and audit API token usage and renewal activities closely to detect abnormal token renewals or extensions beyond expected lifetimes. 2. Restrict privileges to the minimum necessary for token renewal operations to reduce the risk of exploitation by low-privilege users. 3. Implement network segmentation and access controls to limit exposure of the Oxide Omicron control plane to trusted management networks only. 4. Employ multi-factor authentication and additional verification steps for token renewal processes if supported by the platform. 5. 6. Consider temporary compensating controls such as manual token revocation or shortened token lifetimes if configurable. 7. Conduct regular security assessments and penetration tests focusing on token management and control plane security. 8. Prepare incident response plans that include scenarios involving token misuse or persistence mechanisms.

Description

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

Impact

For European organizations, this vulnerability poses a risk of prolonged unauthorized access to critical control plane functions due to the ability to renew API tokens past expiration. While confidentiality is not directly impacted, the integrity of system operations can be compromised, potentially allowing attackers to manipulate configurations or operational parameters. This can lead to operational disruptions or facilitate further attacks such as privilege escalation or lateral movement. Organizations in sectors such as telecommunications, energy, finance, and government that use Oxide Omicron for infrastructure management are particularly at risk. The persistence enabled by this vulnerability complicates incident response and recovery efforts. Additionally, the vulnerability’s requirement for some privileges means insider threats or attackers who have already breached perimeter defenses could exploit it to maintain or escalate access. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits once the vulnerability becomes widely known.

CWE-420Unprotected Alternate Channel (opens in a new tab)
Base weakness
The product protects a primary channel, but it does not use the same level of protection for an alternate channel.
Architecture and Design
Identify all alternate channels and use the same protection mechanisms that are used for the primary channels.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
OWASP ASVS 4.0.3
V1.14.1 (opens in a new tab)
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Dec 2025, 05:31 UTC

WeaknessesCWE-420

Technical details

References

Community reviews

Related threats