dbcve.org
CWE-489Weakness · CWE-489

CVE-2026-54798

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
Remotely reachable 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 includes a debugging interface that is accessible through HTTP endpoints. This could allow an authenticated attacker to disrupt the system by crashing the web process causing denial of service conditions.

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 CPCI85 Central Processing/Communication and SICORE Base system versions prior to V26.20. A debugging interface is exposed through HTTP endpoints, allowing authenticated attackers to crash the web process and cause denial of service.

MitigationDisable or restrict access to the debugging interface through HTTP endpoints. If the debugging functionality is not needed in production, it should be completely removed or firewall rules should be applied to prevent external access.

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 product and version
    Locate the installed version of CPCI85 Central Processing/Communication or SICORE Base system through the product's version information interface, About screen, or system configuration file
    Affected if Version is displayed as prior to V26.20 (for example, V26.19, V25.x, etc.)
  2. Confirm product type
    Verify that the affected system is either CPCI85 Central Processing/Communication or SICORE Base system
    Affected if The installed product is CPCI85 or SICORE Base and version is below V26.20
  3. Check HTTP debugging endpoint exposure
    Inspect network configuration or firewall rules to determine if HTTP debugging interfaces are accessible via web browser or HTTP tools to unauthenticated or authenticated users
    Affected if HTTP debugging endpoints are exposed and accessible over the network
  4. Test web process stability
    If debugging endpoints are accessible, attempt to send requests to known debugging paths to observe if the web process crashes or becomes unresponsive
    Affected if The web process crashes or becomes unresponsive when accessing debugging interfaces

The environment is affected if CPCI85 Central Processing/Communication or SICORE Base system with a version prior to V26.20 has an exposed HTTP debugging interface that can be accessed to crash the web process.

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

Disable or restrict access to the debugging interface through HTTP endpoints. If the debugging functionality is not needed in production, it should be completely removed or firewall rules should be applied to prevent external access.

Recommended fix High confidence

CPCI85: V26.20 or later; SICORE Base system: V26.20.0 or later

  1. 1. Identify the currently installed version of CPCI85 Central Processing/Communication or SICORE Base system
  2. 2. Back up all current configurations and data according to your organization's backup procedures
  3. 3. Obtain the upgrade package for version V26.20 or later from the vendor (Siemens)
  4. 4. Review the vendor's upgrade documentation for any specific prerequisites
  5. 5. Execute the upgrade process following Siemens' official upgrade instructions
  6. 6. After upgrade, verify that the debugging HTTP endpoints are no longer accessible or have been disabled
  7. 7. Test that the web interface and critical functions operate normally
  8. 8. Confirm the new version number matches the fixed release (V26.20 or later)
Caveat Review Siemens release notes for any changes in functionality or configuration requirements between your current version and V26.20

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54798 — 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-54798 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