# CVE-2026-78225: Wärtsilä FOS-Onboard Use of Hard-coded Cryptographic Key

> Attackers can exploit a hardcoded cryptographic key in the Wärtsilä FOS-Onboard update controller to bypass security controls and potentially execute code.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-xr64-qq65-vf4r

## What is CVE-2026-78225?

CVE-2026-78225 is a critical vulnerability in Wärtsilä FOS-Onboard, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A hardcoded cryptographic server key vulnerability exists in the deployer-ng Update Controller component of Wärtsilä FOS-Onboard.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2026-78225 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78225 is a critical vulnerability in Wärtsilä FOS-Onboard, published on 15 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-78225 in the wild and no public exploit code.

Affected product: Wärtsilä FOS-Onboard. 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-78225/ (Markdown: https://insights.sbomify.com/CVE-2026-78225/index.md)
```

## Sources

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

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