dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2026-33554

HIGH · 7.5 CVSS v3.1 Published 2026-03-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
ipmi-oem in FreeIPMI before 1.6.17 has exploitable buffer overflows on response messages. The Intelligent Platform Management Interface (IPMI) specification defines a set of interfaces for platform management. It is implemented by a large number of hardware manufacturers to support system management. It is most commonly used for sensor reading (e.g., CPU temperatures through the ipmi-sensors command within FreeIPMI) and remote power control (the ipmipower command). The ipmi-oem client command implements a set of a IPMI OEM commands for specific hardware vendors. If a user has supported hardware, they may wish to use the ipmi-oem command to send a request to a server to retrieve specific information. Three subcommands were found to have exploitable buffer overflows on response messages. They are: "ipmi-oem dell get-last-post-code - get the last POST code and string describing the error on some Dell servers," "ipmi-oem supermicro extra-firmware-info - get extra firmware info on Supermicro servers," and "ipmi-oem wistron read-proprietary-string - read a proprietary string on Wistron servers."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Buffer overflow vulnerability in FreeIPMI ipmi-oem command's response message parsing. Three subcommands (dell get-last-post-code, supermicro extra-firmware-info, and wistron read-proprietary-string) fail to properly validate buffer sizes when processing IPMI device responses, allowing controllable overflow with potential for code execution.

MitigationUpgrade FreeIPMI to version 1.6.17 or later. Until patched, avoid using the three affected subcommands or isolate IPMI management networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if FreeIPMI is installed
    Run command: which ipmi-oem or rpm -q freeipmi or dpkg -l | grep freeipmi
    Affected if FreeIPMI ipmi-oem command is present on the system
  2. Determine installed FreeIPMI version
    Run command: ipmi-oem -V or rpm -q freeipmi or dpkg -l freeipmi
    Affected if Version is 1.6.16 or earlier (vulnerable); version 1.6.17 and later are patched
  3. Verify ipmi-oem executable version string
    Run: ipmi-oem --help 2>&1 | head -5 or ipmi-oem -v 2>&1
    Affected if Version displayed as 1.6.16 or lower indicates vulnerability
  4. Identify usage of affected subcommands
    Search for automated scripts or cron jobs containing: 'ipmi-oem dell get-last-post-code', 'ipmi-oem supermicro extra-firmware-info', or 'ipmi-oem wistron read-proprietary-string'
    Affected if Any of these three subcommands are actively used in scripts or automation

If FreeIPMI version is 1.6.16 or earlier AND any of the three affected subcommands (dell get-last-post-code, supermicro extra-firmware-info, wistron read-proprietary-string) are used, the system is vulnerable to CVE-2026-33554.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade FreeIPMI to version 1.6.17 or later. Until patched, avoid using the three affected subcommands or isolate IPMI management networks.

Recommended fix High confidence

FreeIPMI 1.6.17

  1. Check current FreeIPMI version by running 'ipmi-oem --version' or 'rpm -q freeipmi' / 'dpkg -l freeipmi'
  2. Download FreeIPMI version 1.6.17 or later from the official GNU FTP (ftp.gnu.org) or compile from source
  3. If using a package manager, wait for your distribution to push the fixed package (1.6.17+) or manually upgrade using distribution-specific commands
  4. After upgrading, verify the fix by running 'ipmi-oem dell get-last-post-code', 'ipmi-oem supermicro extra-firmware-info', or 'ipmi-oem wistron read-proprietary-string' on a test system to confirm no buffer overflow occurs
  5. Ensure any IPMI management scripts or automation using ipmi-oem are tested after the upgrade
Caveat Minimal risk - this is a bugfix release addressing security vulnerabilities; however, test OEM command functionality with your specific hardware after upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33554 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33554 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data