CVE-2025-8404VulnerabilityPublished 18 Nov 2025Updated 19 Nov 2025

CVE-2025-8404: SMCI MBD-X13SEDW-F · Stack-based Buffer Overflow

Affects SMCI MBD-X13SEDW-FSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.5Medium

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

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

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

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

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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; 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 impacted component (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).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 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
SMCI MBD-X13SEDW-F	Affected =01.03.48	Fixed in–

AI-suggested

1. Restrict BMC network access strictly to trusted administrators and management networks using network segmentation and firewall rules. 2. Enforce strong authentication mechanisms for BMC access, including multi-factor authentication where possible. 3. Monitor BMC logs and network traffic for anomalous or unexpected activity, especially crafted headers or unusual command sequences. 4. Disable unnecessary BMC services or interfaces to reduce the attack surface. 5. Maintain an inventory of affected hardware and firmware versions to prioritize risk assessment. 6. Engage with Supermicro for timely patch releases and apply firmware updates as soon as they become available. 7. Consider implementing hardware-based protections such as Trusted Platform Modules (TPMs) or secure boot features to detect unauthorized firmware modifications. 8. Conduct regular security audits and penetration testing focused on BMC interfaces. 9. Educate system administrators about the risks associated with BMC vulnerabilities and the importance of secure management practices. 10. Prepare incident response plans that include scenarios involving BMC compromise.

Description

Stack buffer overflow vulnerability exists in the Supermicro BMC Shared library. An authenticated attacker with access to the BMC exploit stack buffer via a crafted header and achieve arbitrary code execution of the BMC’s firmware operating system.

Impact

For European organizations, the impact of CVE-2025-8404 can be significant, particularly for data centers, cloud providers, and enterprises relying on Supermicro MBD-X13SEDW-F motherboards for critical infrastructure. Successful exploitation could allow attackers to execute arbitrary code on the BMC firmware, potentially leading to unauthorized control over server management functions, disruption of hardware operations, or persistent firmware-level compromise. This could result in denial of service conditions, manipulation of server states, or evasion of traditional OS-level security controls. Although confidentiality is not directly affected, the integrity and availability of critical management functions are at risk, which can indirectly impact data security and operational continuity. Given the BMC’s role in out-of-band management, attackers could bypass OS-level protections and maintain stealthy persistence. European organizations with stringent compliance and uptime requirements may face operational and reputational damage if this vulnerability is exploited. The lack of patches and known exploits in the wild currently reduces immediate risk but also means organizations must rely on preventive controls.

CWE-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

supermicro.com/zh_tw/support/security_BMC_IPMI_Nov_2025 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Nov 2025, 08:42 UTC

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats