# CVE-2026-54799: Security feature bypass in CPCI85 Central Processing/Communication

> Attackers can bypass firmware signature validation to install malicious firmware, achieving persistent code execution on Siemens CPCI85 and SICORE systems.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 9 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-j26p-j946-5hv2

## What is CVE-2026-54799?

CVE-2026-54799 is a high-severity vulnerability in Siemens CPCI85 Central Processing/Communication, published on 9 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been identified in CPCI85 Central Processing/Communication (All versions < V26.20), SICORE Base system (All versions < V26.20.0). The affected application contains a vulnerability in its firmware update mechanism's signature validation process. This could allow an attacker to install malicious firmware, leading to persistent code execution and system compromise.

Weakness: CWE-489 (Active Debug Code)

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


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

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

## Is CVE-2026-54799 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54799 is a high-severity vulnerability in Siemens CPCI85 Central Processing/Communication, published on 9 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-54799 in the wild and no public exploit code.

Affected product: Siemens CPCI85 Central Processing/Communication. 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-54799/ (Markdown: https://insights.sbomify.com/CVE-2026-54799/index.md)
```

## Sources

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

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