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

CVE-2026-50031

HIGH · 7.5 CVSS v3.1 Published 2026-06-03
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.18 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. Two subcommands "ipmi-oem dell get-active-directory-config" and "ipmi-oem fujitsu get-sel-entry-long-text" were found to have exploitable buffer overflows on response messages.

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 · moderate confidence

The ipmi-oem client command in FreeIPMI versions before 1.6.18 contains exploitable buffer overflows when processing response messages. Specifically, the 'ipmi-oem dell get-active-directory-config' and 'ipmi-oem fujitsu get-sel-entry-long-text' subcommands fail to properly bounds-check data received from IPMI servers, potentially allowing remote code execution or denial of service via specially crafted malicious responses.

MitigationUpdate FreeIPMI to version 1.6.18 or later to obtain the patched binaries. As a client-side vulnerability, also exercise caution when connecting to untrusted or unknown IPMI servers.

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. Verify FreeIPMI installation and version
    Run 'ipmi-oem --version' or 'freeipmi-version' to determine the installed FreeIPMI version
    Affected if The version is present and is earlier than 1.6.18
  2. Confirm ipmi-oem binary exists
    Check for the ipmi-oem binary in the system PATH (e.g., run 'which ipmi-oem')
    Affected if The ipmi-oem binary is found on the system
  3. Identify usage of vulnerable subcommands
    Review any scripts, automation, or manual commands that invoke 'ipmi-oem dell get-active-directory-config' or 'ipmi-oem fujitsu get-sel-entry-long-text'
    Affected if These specific subcommands are used to communicate with IPMI devices
  4. Assess trust level of IPMI devices
    Examine which IPMI devices the ipmi-oem tool connects to; check configuration files, inventory lists, or connection logs
    Affected if The tool connects to untrusted or potentially compromised IPMI devices when using the affected subcommands

A user is affected if FreeIPMI version is earlier than 1.6.18 AND the 'dell get-active-directory-config' or 'fujitsu get-sel-entry-long-text' subcommands are used to interact with IPMI devices.

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

Update FreeIPMI to version 1.6.18 or later to obtain the patched binaries. As a client-side vulnerability, also exercise caution when connecting to untrusted or unknown IPMI servers.

Recommended fix High confidence

FreeIPMI 1.6.18 or later

  1. Check current FreeIPMI version by running 'ipmi-oem --version' or 'rpm -q freeipmi' / 'dpkg -l freeipmi'
  2. Download FreeIPMI version 1.6.18 or later from the official GNU FreeIPMI distribution (savannah.gnu.org/projects/freeipmi)
  3. Upgrade the package using your system's package manager: 'sudo apt-get update && sudo apt-get install freeipmi' (Debian/Ubuntu) or 'sudo yum update freeipmi' (RHEL/CentOS)
  4. Alternatively, compile from source: download tarball, run './configure', 'make', 'sudo make install'
  5. Verify the upgrade was successful by running 'ipmi-oem --version' and confirming the version is 1.6.18 or later
  6. Test that the affected subcommands 'ipmi-oem dell get-active-directory-config' and 'ipmi-oem fujitsu get-sel-entry-long-text' function normally with the updated version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50031 — 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-50031 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