Skip to content
Systems

CVE-2026-54801

8.6
High
EPSS 0.62%Patch availableJul 10, 2026

Authenticated users can escalate to admin via flawed web API credential validation.

common questions

Is CVE-2026-54801 being exploited?

Not confirmed. CVE-2026-54801 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.62% probability of exploitation in the next 30 days.

How severe is CVE-2026-54801?

CVE-2026-54801 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-54801?

Yes. A fix has been recorded for CVE-2026-54801. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-54801 affect?

CVE-2026-54801 affects CPCI85 Central Processing/Communication (< V26.20), SICORE Base system (< V26.20.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-54801?

Upgrade to V26.20 or apply vendor patch; restrict/segregate admin API access and rotate admin credentials.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
CPCI85 Central Processing/Communication (< V26.20)SICORE Base system (< V26.20.0)
impact

Authenticated attacker can bypass API auth to gain administrative privileges, permitting config changes, account takeover, and persistent access.

action required

Immediate action required

affected versions
Siemens CPCI85 Central Processing/Communication
  • affected< V26.20
Siemens SICORE Base system
  • affected< V26.20.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free