# CVE-2026-16707: Power System Out-of-bounds Read

> An attacker with authenticated service-level access can read or modify arbitrary host firmware memory via the service processor mailbox interface.

- **Severity:** High 8.2 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 19 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-8pm5-m8h3-36ww

## What is CVE-2026-16707?

CVE-2026-16707 is a high-severity memory corruption vulnerability in IBM PowerVM Hypervisor, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM PowerVM Hypervisor FW1120.00, FW1110.00 through FW1110.30, FW1060.00 through FW1060.80, and FW950.00 through FW950.H2 is affected by a vulnerability in the service processor mailbox interface. An attacker with authenticated service-level access to the FSP can send a specially crafted mailbox message to read or modify arbitrary regions of Hostboot memory, compromising the host firmware boot stack and the hypervisor subsequently loaded by it. Successful exploitation results in a confidentiality, integrity, and availability impact to the managed system.

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

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

It affects 26 products.


Products: Ibm Power System E1050 \(9043-Mrx\) Firmware, Ibm Power System E1080 \(9080-Hex\) Firmware, Ibm Power System E1150 \(9043-Mru\) Firmware, Ibm Power System E1180 \(9080-Heu\) Firmware, Ibm Power System E950 \(9040-Mr9\) Firmware, Ibm Power System E980 \(9080-M9s\) Firmware, Ibm Power System H922 \(9223-22s\) Firmware, Ibm Power System H924 \(9223-42s\) 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 and 6 more.

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

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

## Is CVE-2026-16707 being exploited?

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

## Other vulnerabilities in IBM PowerVM Hypervisor

- [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-16930](https://insights.sbomify.com/CVE-2026-16930/): Power System Missing Authorization (high 8.2)
- [CVE-2026-19234](https://insights.sbomify.com/CVE-2026-19234/): Power System Buffer Overflow (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16707 is a high-severity memory corruption vulnerability in IBM PowerVM Hypervisor, published on 19 Aug 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-16707 in the wild and no public exploit code.

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

## Sources

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

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