CVE-2025-27243VulnerabilityPublished 10 Feb 2026

CVE-2025-27243: Intel(R) Ethernet Controller E810 · Denial of Service

Affects Intel(R) Ethernet Controller E810Source CVE Database V5

Not known to be exploited · CVSS 6.7 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.7Medium

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:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: High
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: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
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 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
Intel(R) Ethernet Controller E810	Affected =before version cvl fw 1.7.8.x	Fixed in–

AI-suggested

1. Immediately verify the firmware version of Intel Ethernet Controller E810 devices and upgrade to version cvl fw 1.7.8.x or later where the vulnerability is patched. 2. Restrict and monitor privileged user access on systems with affected hardware to reduce the risk of local exploitation. 3. Implement strict access controls and auditing for administrative accounts to detect and prevent unauthorized privilege escalation. 4. Employ network segmentation to isolate critical systems using vulnerable controllers, limiting the impact of potential denial of service events. 5. Regularly review and update firmware and driver inventories as part of asset management to ensure timely patching of vulnerabilities. 6. Conduct internal security awareness training emphasizing the risks of privileged account misuse. 7. Monitor system logs and network behavior for signs of instability or unusual activity that could indicate exploitation attempts. 8. Coordinate with Intel and hardware vendors for any additional security advisories or mitigations related to this vulnerability.

Description

Out-of-bounds write in the firmware for some Intel(R) Ethernet Controller E810 before version cvl fw 1.7.8.x within Ring 0: Bare Metal OS may allow a denial of service. System software adversary with a privileged user combined with a low complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.

Impact

For European organizations, the primary impact of CVE-2025-27243 is the potential disruption of network availability due to denial of service conditions on systems using vulnerable Intel Ethernet Controller E810 firmware. This can affect data centers, enterprise servers, and critical infrastructure relying on these network controllers for stable connectivity. Service interruptions may lead to operational downtime, impacting business continuity, especially in sectors like finance, telecommunications, healthcare, and government services. Since the vulnerability requires privileged local access, the risk is heightened in environments where insider threats or compromised administrative accounts exist. Although confidentiality and integrity are not directly affected, the loss of availability can indirectly impact organizational operations and service delivery. The absence of known exploits reduces immediate risk but does not eliminate the need for proactive mitigation. Organizations with extensive deployments of Intel Ethernet Controller E810 hardware should prioritize firmware updates to prevent potential exploitation.

References

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

Community reviews

Loading reviews…