# CVE-2026-85505: Memory corruption in FreeIPMI

> A stack-based buffer over-read in FreeIPMI allows attackers to cause denial of service or disclose information via a short BMC response.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 8 Sep 2026
- **Also known as:** AZL-99107, BELL-CVE-2026-85505, DEBIAN-CVE-2026-85505, GHSA-386j-5xxr-g7c7, UBUNTU-CVE-2026-85505

## What is CVE-2026-85505?

CVE-2026-85505 is a high-severity 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 over-read in ipmi_oem_fujitsu_get_sel_entry_long_text in ipmi-oem/ipmi-oem-fujitsu.c when a BMC provides a short response, a different vulnerability than CVE-2026-50031 (which has different affected versions).

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Upgrade to a fixed version.

## Is CVE-2026-85505 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85505 is a high-severity 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-85505 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-85505/ (Markdown: https://insights.sbomify.com/CVE-2026-85505/index.md)
```

## Sources

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

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