Process memory corruption via unchecked BMC response length
Published Sep 4, 2026 · Updated Sep 4, 2026
Stack-based buffer overflow in GNU Project FreeIPMI before 1.6.19 allows remote attackers to corrupt process memory via a crafted BMC response. The _get_dell_system_info_idrac_info loop appends three BMC-controlled blocks into a 256-byte idrac_info stack buffer without checking the cumulative offset before memcpy. Exploitation requires the idrac-info path to process a malicious Dell iDRAC response; publicly retrieved sources do not establish code execution beyond the resulting stack corruption.
Summary
What happened
Stack-based buffer overflow in GNU Project FreeIPMI before 1.6.19 allows remote attackers to corrupt process memory via a crafted BMC response. The _get_dell_system_info_idrac_info loop appends three BMC-controlled blocks into a 256-byte idrac_info stack buffer without checking the cumulative offset before memcpy. Exploitation requires the idrac-info path to process a malicious Dell iDRAC response; publicly retrieved sources do not establish code execution beyond the resulting stack corruption.
The record
- CVE
- CVE-2026-85506
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- Vendor
- The GnuPG Project
- Product
- FreeIPMI
- Classifications
- CWE-121, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 4, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.6.19
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo