dbcve.org
CWE-489Weakness · CWE-489

CVE-2026-54799

MEDIUM · 6.7 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The vulnerability exists in the firmware update mechanism's signature validation process for CPCI85 and SICORE Base systems. An attacker could exploit this by providing maliciously crafted firmware that bypasses cryptographic signature checks, allowing persistent code execution on the affected devices.

MitigationUpgrade to version V26.20 (CPCI85) or V26.20.0 (SICORE) or later which contains the signature validation fix. If immediate patching is not possible, restrict network and physical access to the firmware update interface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the product model
    Locate the system nameplate, web interface, or administrative console to determine if the device is a CPCI85 or SICORE Base system.
    Affected if The device is a CPCI85 or SICORE Base system running firmware versions V26.20 (CPCI85) or V26.20.0 (SICORE) or earlier.
  2. Determine the installed firmware version
    Access the device administrative interface or use the vendor-supplied firmware version query command (typically via CLI or web UI under System Information or About). Compare the reported version to the affected ranges.
    Affected if The installed version is V26.20 or earlier for CPCI85, or V26.20.0 or earlier for SICORE Base.
  3. Verify the firmware update interface is accessible
    Check if the device exposes a firmware update or software update function through the web interface, CLI, or network service. Look for update/upgrade menu options or check for open update-related ports or API endpoints.
    Affected if The firmware update interface is exposed and accessible (web, network service, or CLI update command).
  4. Confirm whether signature validation is enforced
    Inspect the device configuration settings for firmware update security options. Look for settings related to signature verification, code signing, or secure boot. If available, check logs or status for any signature validation errors during recent update attempts.
    Affected if Signature validation is disabled, not enforced, or the configuration allows unsigned firmware uploads.
  5. Review recent firmware update history
    Examine system logs, audit logs, or update history records for any firmware updates performed on the device. Note the source and whether signature verification was logged as passing.
    Affected if Firmware updates were performed from external or untrusted sources, or signature validation status is unclear or not logged.

A user is affected if they have a CPCI85 or SICORE Base system running firmware version V26.20 (CPCI85) or V26.20.0 (SICORE) or earlier, with the firmware update interface accessible and signature validation not confirmed as enforced.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version V26.20 (CPCI85) or V26.20.0 (SICORE) or later which contains the signature validation fix. If immediate patching is not possible, restrict network and physical access to the firmware update interface.

Recommended fix Moderate confidence

V26.20 (CPCI85) / V26.20.0 (SICORE Base system)

  1. Identify the current firmware version of the CPCI85 Central Processing/Communication device or SICORE Base system
  2. Download the updated firmware version V26.20 (for CPCI85) or V26.20.0 (for SICORE Base system) from the official Siemens cert-portal or authorized distribution channel
  3. Verify the firmware package integrity using provided checksums or digital signatures
  4. Follow the manufacturer's documented firmware update procedure for the specific device, typically involving entering maintenance/boot mode
  5. Upload and install the firmware, ensuring stable power supply throughout the process
  6. After installation, verify the new firmware version is correctly installed
  7. Reboot the device to ensure the new firmware is fully operational

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54799 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54799 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data