# CVE-2026-16607: Authenticated local root privilege escalation vulnerability in openFT for Linux and Oracle Solaris

> An authenticated local user can escalate privileges to root on Fujitsu openFT for Linux and Oracle Solaris.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-rr2p-3q6v-qr2f

## What is CVE-2026-16607?

CVE-2026-16607 is a high-severity vulnerability in Fujitsu Linux openFT, published on 22 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in Fujitsu Software Linux openFT and Fujitsu Software Oracle Solaris openFT before version 12.1D00 allows for local privilege escalation to root of an already authenticated user on GNU/Linux or Oracle Solaris. The Fsas Technologies PSIRT obtained that intelligence internally and covers the CVE beyond its CNA scope under existing agreement with Fujitsu Germany.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-16607 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16607 is a high-severity vulnerability in Fujitsu Linux openFT, published on 22 Jul 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-16607 in the wild and no public exploit code.

Affected product: Fujitsu Linux openFT. 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-16607/ (Markdown: https://insights.sbomify.com/CVE-2026-16607/index.md)
```

## Sources

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

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