Security readout for executives and security teams
Plain-English summary
FreeIPMI versions before 1.6.19 can mishandle an oversized response from a baseboard management controller (BMC), overflowing process memory. A compromised or faulty BMC could therefore crash an affected FreeIPMI process and may cause broader confidentiality, integrity, or availability impact. The supplied sources do not establish real-world exploitation.
Executive priority
Treat remediation as urgent for systems using vulnerable FreeIPMI against reachable BMCs, especially critical infrastructure and shared management networks. Accelerate inventory and patching, but do not characterize this as an active incident solely from the supplied evidence. Validate management-network segmentation while updates are deployed.
Technical view
CVE-2026-85509 is a stack-based buffer overflow (CWE-121) in _read_fru_data within libfreeipmi/fru/ipmi-fru.c. It occurs when a BMC returns more FRU-data bytes than FreeIPMI requested. The supplied CVSS 3.1 rating is 9.8, with network reachability, low complexity, no privileges, and no user interaction represented in its vector.
Likely exposure
Exposure is most likely where FreeIPMI earlier than 1.6.19 communicates with BMCs, including management, monitoring, or automation systems. Practical reachability depends on deployment architecture and which systems or networks can influence BMC responses. The bundle's structured affected-version entry is incomplete, so validate installed versions directly.
Exploitation context
The vulnerability requires an affected FreeIPMI process to receive an oversized response from a BMC. This makes compromised, malicious, or malfunctioning BMC communication the relevant risk context. CVE-2026-85509 is not listed as KEV in the supplied bundle, and no cited source here confirms active exploitation or a public exploit.
Researcher notes
The vulnerable condition is an excessive BMC response during FRU-data handling. The supplied record identifies the function and source file but does not provide enough evidence to determine reliable code execution, affected distributions, or exact runtime preconditions. The structured affected entry contains version "0" while the description says versions before 1.6.19; use the latter cautiously and verify vendor packaging.
Mitigation direction
- Upgrade FreeIPMI to version 1.6.19 or a later vendor-supported release.
- Prioritize hosts that query BMCs across exposed or less-trusted management networks.
- Restrict BMC and IPMI communication to authorized management systems and isolated networks.
- Consult GNU FreeIPMI and operating-system vendor guidance for packaged updates.
Validation and detection
- Inventory FreeIPMI and libfreeipmi versions; flag installations earlier than 1.6.19.
- Identify services, scripts, and monitoring tools that retrieve FRU data through FreeIPMI.
- Confirm BMC interfaces are reachable only from approved management hosts and networks.
- Review affected processes for crashes or memory-corruption indicators during BMC interactions.
- Verify upgraded packages report version 1.6.19 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-121: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-85509 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9mitreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.openwall.com/lists/oss-security/2026/08/28/5CVE reference, mitre
- https://www.gnu.org/software/freeipmi/CVE reference, mitre
- https://ftp.gnu.org/gnu/freeipmi/freeipmi-1.6.19.tar.gzCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.