CVE-2026-56451

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreHIGH confidence

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-14. a secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 10.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A vulnerability has been identified in Opcenter X (All versions < V2604). Affected applications do not properly validate the algorithm specified in the JSON Web Token (JWT) header. This could allow an unauthenticated remote attacker to forge arbitrary JWT, bypass authentication mechanisms and impersonate any user including administrative accounts, potentially gaining full unauthorized access to the application.

CVSS v3
10.0
EG Score
10.0(high)
EG Risk
60(Track)
EG Risk 60/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
30.9%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated Jul 23, 2026
No patch confirmed yet.
generic

SSA-096828

https://cert-portal.siemens.com/productcert/html/ssa-096828.html

Vendor Advisories for CVE-2026-56451(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:20 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-17 05:32 UTCGHSA enrichment
  11. 2026-07-17 01:20 UTCGHSA enrichment
  12. 2026-07-16 21:09 UTCGHSA enrichment
  13. 2026-07-16 17:03 UTCEPSS rescore
  14. 2026-07-16 16:57 UTCGHSA enrichment
  15. 2026-07-16 12:23 UTCGHSA enrichment
  16. 2026-07-16 08:11 UTCGHSA enrichment
  17. 2026-07-16 03:59 UTCGHSA enrichment
  18. 2026-07-15 23:47 UTCGHSA enrichment
  19. 2026-07-15 19:35 UTCGHSA enrichment
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 15:23 UTCGHSA enrichment
  23. 2026-07-15 11:10 UTCGHSA enrichment
  24. 2026-07-15 06:58 UTCGHSA enrichment
  25. 2026-07-15 02:44 UTCGHSA enrichment
Show 7 more
  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-14 22:32 UTCGHSA enrichment
  4. 2026-07-14 18:20 UTCGHSA enrichment
  5. 2026-07-14 14:08 UTCGHSA enrichment
  6. 2026-07-14 09:56 UTCEG score recompute
  7. 2026-07-14 09:55 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56451?
CVE-2026-56451 is a critical vulnerability published on July 14, 2026. A vulnerability has been identified in Opcenter X (All versions < V2604). Affected applications do not properly validate the algorithm specified in the JSON Web Token (JWT) header. This could allow an unauthenticated remote attacker to forge arbitrary JWT, bypass authentication mechanisms and…
When was CVE-2026-56451 disclosed?
CVE-2026-56451 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56451 actively exploited?
CVE-2026-56451 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 30.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56451?
CVE-2026-56451 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-56451?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56451, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56451

Explore →

Is Your Infrastructure Affected by CVE-2026-56451?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs