# CVE-2026-85507: Memory corruption in FreeIPMI

> A stack-based buffer overflow in FreeIPMI allows attackers to execute arbitrary code or cause denial of service via the dell get-system-info command.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** AZL-99116, BELL-CVE-2026-85507, DEBIAN-CVE-2026-85507, GHSA-pcp5-vqr5-x65j, UBUNTU-CVE-2026-85507

## What is CVE-2026-85507?

CVE-2026-85507 is a critical memory corruption vulnerability in FreeIPMI, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ipmi-oem in FreeIPMI before 1.6.19 has a stack-based buffer overflow in _output_dell_system_info_cmc_info in ipmi-oem/ipmi-oem-dell.c (cmc-info subcommand to dell get-system-info).

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-85507?


## How do I fix CVE-2026-85507?

Upgrade to a fixed version.

## Is CVE-2026-85507 being exploited?

There is no known exploitation of CVE-2026-85507 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85507 and fix it if it is affected.

What it is: CVE-2026-85507 is a critical memory corruption vulnerability in FreeIPMI, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85507 in the wild and no public exploit code.

Affected product: FreeIPMI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85507/ (Markdown: https://insights.sbomify.com/CVE-2026-85507/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85507
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85507
- OSV: https://osv.dev/vulnerability/CVE-2026-85507

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85507/
Summaries are generated and may contain mistakes; the official description above is the record.