# CVE-2026-16678: IBM Power Systems Firmware Denial of Service

> A remote authenticated attacker can cause a denial of service in IBM Power Systems Firmware by exhausting connection resources due to improper resource management.

- **Severity:** Medium 4.5 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:N/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:** 12 Oct 2026
- **Updated:** 12 Oct 2026
- **Also known as:** GHSA-ff7h-h85h-qx3m

## What is CVE-2026-16678?

CVE-2026-16678 is a medium-severity denial of service vulnerability in IBM Virtualization Management Interface, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IBM Power Systems Firmware FW1110.00 through FW1110.31, FW1120.00 through FW1120.01, and FW1060.00 through FW1060.81 could allow a remote authenticated attacker to cause a denial of service by exhausting connection resources due to improper resource management.

Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime)

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


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

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

## Is CVE-2026-16678 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16678 is a medium-severity denial of service vulnerability in IBM Virtualization Management Interface, published on 12 Oct 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-16678 in the wild and no public exploit code.

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

## Sources

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

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