Siemens Opcenter X JWT auth bypass flaw
A JWT algorithm validation flaw in Siemens Opcenter X before V2604 lets unauthenticated attackers forge tokens and gain full admin access.
Sourcecisa.gov — open the original
What to check
- Applies to
- The 1 CVE named below. Whether you run an affected version is not assessed: check the versions the source lists.
- Exploitation
- No exploitation in the wild and no public exploit is recorded for the CVEs named.
Siemens has disclosed CVE-2026-56451, an authentication bypass vulnerability affecting Opcenter X versions prior to V2604. The flaw stems from improper validation of the algorithm specified in the JSON Web Token (JWT) header, allowing an unauthenticated remote attacker to forge arbitrary JWTs. This effectively bypasses authentication mechanisms and enables impersonation of any user, including administrative accounts, granting full unauthorized access to the application.
Opcenter X is deployed worldwide in critical manufacturing environments. Siemens has released V2604 as a vendor fix and recommends immediate update. No known exploitation in the wild is reported; this is a vendor-disclosed advisory published via CISA with standard ICS network segmentation and VPN mitigation guidance.
Mentioned in this report
Detection guidance
JWT Algorithm Confusion / alg=none Bypass Attempt
A behavioural hunt for the technique in general, not a signature for the CVEs this report names.
Detects HTTP requests carrying a JWT bearer token whose header specifies 'alg':'none' or an unexpected/downgraded algorithm - the generic exploitation pattern behind JWT auth-bypass flaws such as CVE-2026-56451 in Opcenter X. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.
title: JWT Algorithm Confusion / alg=none Bypass Attempt
description: Detects HTTP requests where the Authorization Bearer JWT's base64url-encoded
header decodes to an algorithm of "none" or a suspicious/mismatched alg value, a
hallmark of JWT algorithm-confusion authentication bypass attacks against web applications
(e.g. CVE-2026-56451 affecting Siemens Opcenter X).
tags:
- attack.t1606
logsource:
category: proxy
detection:
selection_header:
c-uri|contains: Authorization
selection_jwt_none:
cs-cookie|contains:
- eyJhbGciOiJub25lIn0
- eyJhbGciOiJOb25lIn0
- '"alg":"none"'
- '"alg": "none"'
condition: selection_header and selection_jwt_none
falsepositives:
- Legitimate applications intentionally using unsigned JWTs in trusted internal test
environments
- Security scanners/pentest tools probing for JWT alg confusion as part of authorized
assessments
level: high
id: f443962b-bbb4-5249-b65a-3f4b37ed9bde
status: experimental
author: Vorant
Behavioural rules are generated from public reporting — validate in your environment before deploying.
Source reporting: https://www.cisa.gov/news-events/ics-advisories/icsa-26-202-03
Free public brief. The detections with Splunk SPL already written (plus Elastic and KQL where they apply) are in the app with a free account, no card. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them.
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply) and live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.
It sits in a corpus of 16,436 reports from 149 sources, 661 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.
Create a free account What it costs