VulnerabilityPublished 24 Mar 2026Updated 3 Jun 2026

CVE-2026-33554: freeipmi · CVE-2026-33554 is a high-severity

Affects freeipmiSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.6.17 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.6.17, 1.16.17

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: None: There is no loss of integrity within 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 24 Mar 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

Upgrade FreeIPMI to 1.6.17; the Debian debian/freeipmi package to 1.16.17.

Affected software

Product	Affected	Fixed in
FreeIPMIFreeIPMI	Affected >=0.7.12 <1.6.17	Fixed in 1.6.17
Debiandebian/freeipmi`pkg:deb/debian/freeipmi`Other threats	Affected <1.16.17	Fixed in 1.16.17

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

AI-suggested

To mitigate CVE-2026-33554, organizations should first verify if they use FreeIPMI versions prior to 1.16.17 and identify affected hardware models from Dell, Supermicro, and Wistron. Immediate steps include restricting network access to IPMI interfaces by implementing strict firewall rules and network segmentation to limit exposure to trusted management networks only. Disable or restrict usage of the vulnerable ipmi-oem subcommands if possible. Monitor IPMI logs for unusual or unexpected OEM command activity. Where feasible, upgrade FreeIPMI to version 1.16.17 or later once available to apply the official fix. If patching is delayed, consider deploying intrusion detection or prevention systems with custom signatures to detect malformed IPMI OEM responses indicative of exploitation attempts. Additionally, enforce strong authentication and encryption on IPMI interfaces to reduce unauthorized access risk, even though this vulnerability does not require authentication. Regularly audit and update IPMI firmware and management tools to minimize exposure to similar vulnerabilities.

Description

CVE-2026-33554 is a high-severity vulnerability in FreeIPMI's ipmi-oem client prior to version 1.16.17, involving exploitable buffer overflows in response messages for specific OEM commands. The affected commands target Dell, Supermicro, and Wistron servers, allowing attackers to potentially cause denial of service or crash the IPMI management interface. The vulnerability requires no authentication or user interaction and can be exploited remotely over the network. While it does not impact confidentiality or integrity directly, it severely affects availability of IPMI services. No known exploits are currently reported in the wild. Organizations using FreeIPMI with affected hardware should prioritize patching or mitigating exposure to IPMI interfaces. Countries with significant use of Dell, Supermicro, and Wistron server hardware are at higher risk.

Impact

The primary impact of CVE-2026-33554 is on the availability of IPMI services used for remote management of servers. Successful exploitation can cause buffer overflows that crash the IPMI interface, leading to denial of service conditions. This can disrupt critical management functions such as sensor monitoring, hardware health checks, and remote power control, potentially delaying incident response and maintenance operations. While the vulnerability does not directly compromise confidentiality or integrity, the loss of availability in management interfaces can indirectly increase risk by limiting administrators' ability to detect or respond to other threats. Organizations relying heavily on IPMI for server management, especially those using Dell, Supermicro, or Wistron hardware, may experience operational disruptions. The lack of authentication or user interaction requirements means attackers can exploit this vulnerability remotely with relative ease, increasing the threat surface. Given the widespread use of affected hardware in data centers, cloud providers, and enterprise environments, the impact could be significant if exploited at scale.

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Mar 2026, 20:35 UTC

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats