CVE-2026-8400

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.5% (42nd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-08-05) is not newer than that change (2026-08-10), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-53438 (ENISA EUVD) · GHSA-m4rx-9mrh-59g9 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

IBM WebSphere Application Server 8.5, and 9.0 and IBM WebSphere Application Server - Liberty Continuous delivery has a flaw in the ORB component in IBM SDK, Java Technology Edition, may allow a malicious IIOP server to induce loading and instantation of arbitrary classes.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 5, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Nov 17, 2026
Patch available.
Web page

Security Bulletin: Multiple Vulnerabilities in IBM® Java SDK affect IBM WebSphere Application Server and WebSphere Application Server Liberty due to the July 2026 CPU

https://www.ibm.com/support/pages/node/7282446

Vendor and National Authority Advisories for CVE-2026-8400(3)

These vendors and national cybersecurity authorities published their own advisory mentioning this CVE — often with remediation steps + affected product lists not in NVD. An authority's is an excerpt, in the language it published it in, not translated, and credited to it with a link.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatjava-1.8.0-ibm-1:1.8.0.8.70-1.el8_102026-08-10redhat

These rows come from Red Hat. Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 89× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 761 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 661 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 14:20 UTCEchelonGraph re-scored
  2. 2026-11-22 14:20 UTCVendor advisory
  3. 2026-11-22 14:20 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  5. 2026-11-21 13:48 UTCEchelonGraph re-scored
  6. 2026-11-21 13:48 UTCVendor advisory
  7. 2026-11-21 13:48 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  8. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  9. 2026-11-20 13:16 UTCEchelonGraph re-scored
  10. 2026-11-20 13:16 UTCVendor advisory
  11. 2026-11-20 13:16 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-11-19 12:45 UTCEchelonGraph re-scored
  14. 2026-11-19 12:45 UTCVendor advisory
  15. 2026-11-19 12:44 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  16. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  17. 2026-11-18 12:11 UTCEchelonGraph re-scored
  18. 2026-11-18 12:11 UTCVendor advisory
  19. 2026-11-18 12:11 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  20. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  21. 2026-11-17 11:39 UTCEchelonGraph re-scored
  22. 2026-11-17 11:39 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  24. 2026-11-16 11:07 UTCEchelonGraph re-scored
  25. 2026-11-16 11:07 UTCVendor advisory
Show 75 more
  1. 2026-11-16 11:07 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  2. 2026-11-15 17:03 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  3. 2026-11-15 10:32 UTCEchelonGraph re-scored
  4. 2026-11-15 10:32 UTCVendor advisory
  5. 2026-11-15 10:32 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  6. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-11-14 09:52 UTCEchelonGraph re-scored
  8. 2026-11-14 09:52 UTCVendor advisory
  9. 2026-11-14 09:52 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  10. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-11-13 09:19 UTCEchelonGraph re-scored
  12. 2026-11-13 09:19 UTCVendor advisory
  13. 2026-11-13 09:19 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  14. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-11-12 08:47 UTCEchelonGraph re-scored
  16. 2026-11-12 08:47 UTCVendor advisory
  17. 2026-11-12 08:47 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  18. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  19. 2026-11-11 08:16 UTCEchelonGraph re-scored
  20. 2026-11-11 08:16 UTCVendor advisory
  21. 2026-11-11 08:16 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  22. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-11-10 07:43 UTCEchelonGraph re-scored
  24. 2026-11-10 07:43 UTCVendor advisory
  25. 2026-11-10 07:43 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  26. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  27. 2026-11-09 07:11 UTCEchelonGraph re-scored
  28. 2026-11-09 07:11 UTCVendor advisory
  29. 2026-11-09 07:11 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  30. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  31. 2026-11-08 06:37 UTCEchelonGraph re-scored
  32. 2026-11-08 06:37 UTCVendor advisory
  33. 2026-11-08 06:37 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  34. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  35. 2026-11-07 06:05 UTCEchelonGraph re-scored
  36. 2026-11-07 06:05 UTCVendor advisory
  37. 2026-11-07 06:05 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  38. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  39. 2026-11-06 05:32 UTCEchelonGraph re-scored
  40. 2026-11-06 05:32 UTCVendor advisory
  41. 2026-11-06 05:32 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  42. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  43. 2026-11-05 05:00 UTCEchelonGraph re-scored
  44. 2026-11-05 05:00 UTCVendor advisory
  45. 2026-11-05 05:00 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  46. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  47. 2026-11-04 04:27 UTCEchelonGraph re-scored
  48. 2026-11-04 04:27 UTCVendor advisory
  49. 2026-11-04 04:27 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  50. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  51. 2026-11-03 03:56 UTCEchelonGraph re-scored
  52. 2026-11-03 03:56 UTCVendor advisory
  53. 2026-11-03 03:56 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  54. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  55. 2026-11-02 03:23 UTCEchelonGraph re-scored
  56. 2026-11-02 03:23 UTCVendor advisory
  57. 2026-11-02 03:23 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  58. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  59. 2026-11-01 02:52 UTCEchelonGraph re-scored
  60. 2026-11-01 02:52 UTCVendor advisory
  61. 2026-11-01 02:52 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  62. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  63. 2026-10-31 02:19 UTCEchelonGraph re-scored
  64. 2026-10-31 02:19 UTCVendor advisory
  65. 2026-10-31 02:19 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  66. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  67. 2026-10-30 01:47 UTCEchelonGraph re-scored
  68. 2026-10-30 01:47 UTCVendor advisory
  69. 2026-10-30 01:47 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  70. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  71. 2026-10-29 01:15 UTCEchelonGraph re-scored
  72. 2026-10-29 01:15 UTCVendor advisory
  73. 2026-10-29 01:15 UTCGHSA enrichmentGHSA-m4rx-9mrh-59g9 · GitHub severity HIGH · GitHub CVSS 8.1
  74. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  75. 2026-10-28 00:43 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-8400?
CVE-2026-8400 is a critical-severity vulnerability; its CVE record was published on August 5, 2026. IBM WebSphere Application Server 8.5, and 9.0 and IBM WebSphere Application Server - Liberty Continuous delivery has a flaw in the ORB component in IBM SDK, Java Technology Edition, may allow a malicious IIOP server to induce loading and instantation of arbitrary classes.
When was the CVE record for CVE-2026-8400 published?
The CVE record for CVE-2026-8400 was published on August 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 10, 2026; the record at its source may have been updated since.
Is CVE-2026-8400 actively exploited?
CVE-2026-8400 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-8400?
CVE-2026-8400 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-8400?
A fix for CVE-2026-8400 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-8400 are linked in the Vendor and National Authority Advisories panel on this page. NCSC-NL's advisory for CVE-2026-8400 is also listed there, in Dutch, as NCSC-NL published it; not translated.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-8400?

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