VulnerabilityPublished 10 Feb 2026

CVE-2025-25058: Intel(R) Ethernet 800-Series · Information Disclosure

Affects Intel(R) Ethernet 800-SeriesSource CVE Database V5

Not known to be exploited · CVSS 2.0 Low.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

2.0Low

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

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

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Feb 2026
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 26 Oct 2026.

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 or the CVSS exploit maturity 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
Intel(R) Ethernet 800-Series	Affected =before version 2.2.2.0 (esxi 8.0) & 2.2.3.0 (esxi 9.0)	Fixed in–

AI-suggested

To mitigate CVE-2025-25058, European organizations should: 1) Apply the latest patches and updates from Intel and VMware for the Intel Ethernet 800-Series drivers and ESXi versions, specifically upgrading to versions 2.2.2.0 or later for ESXi 8.0 and 2.2.3.0 or later for ESXi 9.0. 2) Restrict and monitor authenticated local access to ESXi hosts, enforcing strict access controls and multi-factor authentication to reduce the risk of unauthorized exploitation. 3) Implement robust credential management and monitoring to detect potential insider threats or compromised accounts. 4) Conduct regular security audits and vulnerability scans on virtualized infrastructure to identify outdated drivers or hypervisor versions. 5) Use network segmentation and least privilege principles to limit exposure of ESXi hosts and their management interfaces. 6) Employ host-based intrusion detection systems to monitor for suspicious activities on ESXi hosts. These steps go beyond generic advice by focusing on patch management, access control, and monitoring tailored to the virtualization environment and hardware involved.

Description

Improper initialization for some ESXi kernel mode driver for the Intel(R) Ethernet 800-Series before version 2.2.2.0 (esxi 8.0) & 2.2.3.0 (esxi 9.0) within Ring 1: Device Drivers may allow an information disclosure. Unprivileged software adversary with an authenticated user combined with a low complexity attack may enable data exposure. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (low), integrity (none) and availability (none) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

Impact

For European organizations, the impact of CVE-2025-25058 is primarily related to confidentiality risks within virtualized infrastructure environments using VMware ESXi hypervisors with Intel Ethernet 800-Series NICs. Although the severity is low, sensitive data leakage could occur if an attacker gains authenticated local access, which might be possible through compromised credentials or insider threats. This could affect organizations handling sensitive or regulated data, such as financial institutions, healthcare providers, and government agencies. Since the vulnerability does not affect integrity or availability, operational disruption is unlikely. However, any data exposure could lead to compliance issues under GDPR if personal or sensitive data is involved. The low complexity and lack of required user interaction increase the risk that an insider or attacker with limited privileges could exploit this vulnerability. Organizations relying heavily on ESXi virtualization with Intel Ethernet 800-Series hardware should consider the confidentiality implications and address the vulnerability promptly to prevent potential data leaks.

References

intel.com/content/www/us/en/security-center/advisory/intel-sa-01408.html (opens in a new tab)

Community reviews

Loading reviews…