# CVE-2026-18857: This Power System update is being released to address

> A vulnerability in IBM OpenBMC firmware allows the host system to crash the BMC service or read internal memory, impacting confidentiality and availability.

- **Severity:** Low 3.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-34jw-2gcw-f6v2

## What is CVE-2026-18857?

CVE-2026-18857 is a low-severity vulnerability in IBM OPENBMC, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM OPENBMC FW1120.00 through FW1120.01, FW1110.00 through FW1110.31, and FW1060.00 through FW1060.81 is affected by a vulnerability in the BMC firmware management interface. The host system can cause the BMC firmware management service to crash or allow a limited amount of BMC internal memory to be read, resulting in a confidentiality and availability impact to the managed system.

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

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

It affects 17 products.


Products: Ibm Power System E1050 \(9043-Mrx\) Firmware, Ibm Power System E1150 \(9043-Mru\) Firmware, Ibm Power System L1022 \(9786-22h\) Firmware, Ibm Power System L1024 \(9786-42h\) Firmware, Ibm Power System L1122 \(9856-22h\) Firmware, Ibm Power System L1124 \(9856-42h\) Firmware, Ibm Power System S1012 \(9028-21b\) Firmware, Ibm Power System S1014 \(9105-41b\) Firmware, Ibm Power System S1022 \(9105-22a\) Firmware, Ibm Power System S1022s \(9105-22b\) Firmware, Ibm Power System S1024 \(9105-42a\) Firmware, Ibm Power System S1112 \(9242-21b\) Firmware, Ibm Power System S1112 \(9242-21t\) Firmware, Ibm Power System S1114 \(9824-41b\) Firmware, Ibm Power System S1122 \(9824-22a\) Firmware, Ibm Power System S1122s \(9824-22b\) Firmware, Ibm Power System S1124 \(9824-42a\) Firmware.

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

No fix has been published for CVE-2026-18857 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-18857 being exploited?

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

## Other vulnerabilities in IBM OPENBMC

- [CVE-2026-17091](https://insights.sbomify.com/CVE-2026-17091/): Power System Integer Overflow (high 8.4)
- [CVE-2026-11885](https://insights.sbomify.com/CVE-2026-11885/): Power System update in Buffer Copy (high 8.4)
- [CVE-2026-16661](https://insights.sbomify.com/CVE-2026-16661/): Power System Integer Overflow (high 8.2)
- [CVE-2026-16707](https://insights.sbomify.com/CVE-2026-16707/): Power System Out-of-bounds Read (high 8.2)
- [CVE-2026-16930](https://insights.sbomify.com/CVE-2026-16930/): Power System Missing Authorization (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18857 is a low-severity vulnerability in IBM OPENBMC, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18857 in the wild and no public exploit code.

Affected product: IBM OPENBMC. 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-18857/ (Markdown: https://insights.sbomify.com/CVE-2026-18857/index.md)
```

## Sources

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

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