CVE-2026-114938 (Java4Shell)

Known as Java4Shell (source: Calif).

HIGHPre-NVD 8.18.4
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than the CVSS score beside it.

Score elevated to 8.4 because EPSS predicted 46% probability of exploitation within the next 30 days (98th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. A secondary CVSS source baseline 8.1 retained for reference (NVD's own analysis pending). Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this weekElevated

Also known asEUVD-2026-127648 (ENISA EUVD) · GHSA-6g7j-4xh3-xq2q (GitHub Security Advisories)Source: ENISA EUVD

8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 46%CVSS: 8.1Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

Read our analysis: Java4Shell (CVE-2026-114938): Java SE and OpenJDK Fix Guide →

Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Compiler). Supported versions that are affected are Oracle Java SE: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3; Oracle GraalVM for JDK: 17.0.21.0.3 and 21.0.13.0.3; Oracle GraalVM Enterprise Edition: 21.3.20.0.3. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in takeover of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Note: This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).

CVSS v3
8.1
EG Score
8.4HIGHhigh confidence
EG Risk
55
EG Risk 55/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation46% × 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
46%
EPSS %ILE
98th
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 (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 8.1 HIGH): a likelihood of exploitation, not impact.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
46% 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

November 17, 2026

Last Modified

November 20, 2026

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatjava-21-openjdk-main-21.0.13.1.2-0.1.hum12026-11-21redhat
redhatjava-25-openjdk-main-25.0.5.1.2-1.1.hum12026-11-21redhat
redhatjava-25-openjdk-windows2026-11-20redhat
redhatjava-17-openjdk-portable-main-17.0.21.1.2-0.1.hum12026-11-20redhat
redhatjava-21-openjdk-portable-main-21.0.13.1.2-1.0.1.hum12026-11-20redhat
redhatjava-21-openjdk-1:21.0.13.1.2-1.2.el92026-11-19redhat
redhatjava-25-openjdk-1:25.0.5.1.2-1.1.el92026-11-19redhat
redhatjava-25-openjdk-1:25.0.5.1.2-1.1.el102026-11-19redhat
redhatjava-17-openjdk-1:17.0.21.1.2-2.1.el82026-11-19redhat
redhatjava-17-openjdk-1:17.0.21.1.2-2.2.el92026-11-19redhat
redhatjava-21-openjdk-1:21.0.13.1.2-1.2.el102026-11-19redhat
ubuntuopenjdk-21-testsupport (21.0.13.1+2-1~22.04.1) @ jammy2026-11-19ubuntu
ubuntuopenjdk-25-testsupport (25.0.5.1+2-1~26.10.1) @ stonking2026-11-19ubuntu
ubuntuopenjdk-17-source (17.0.21.1+2-1~22.04.1) @ jammy2026-11-19ubuntu
ubuntuopenjdk-27-testsupport (27.0.1.1+4-1~26.10.1) @ stonking2026-11-19ubuntu
redhatjava-17-openjdk-windows2026-11-18redhat
redhatjava-21-openjdk-portable2026-11-18redhat
redhatjava-21-openjdk-windows2026-11-18redhat
redhatjava-17-openjdk-portable2026-11-18redhat
redhatjava-25-openjdk-portable2026-11-18redhat
openjdkOpenJDK 17, 21, 25, 27 updates2026-11-17openjdk
oraclepatch2026-11-17oracle
oracleOracle JDK 17.0.21.12026-11-17oracle
oracleOracle JDK 25.0.5.12026-11-17oracle
oracleOracle JDK 27.0.1.12026-11-17oracle
oracleOracle JDK 21.0.13.12026-11-17oracle

These rows come from Red Hat, Ubuntu, OpenJDK and Oracle. 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.

Additional Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 39× in last 7d / 39× 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.

  1. 2026-11-22 06:39 UTCVendor advisory
  2. 2026-11-21 16:39 UTCEchelonGraph re-scored▲ 0.30
  3. 2026-11-21 16:39 UTCVendor advisory
  4. 2026-11-21 16:39 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  5. 2026-11-21 16:38 UTCEPSS rescoreEPSS 46% · 98th percentile
  6. 2026-11-20 19:28 UTCVendor advisory
  7. 2026-11-20 19:28 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  8. 2026-11-20 17:08 UTCEchelonGraph re-scored
  9. 2026-11-20 17:08 UTCVendor advisory
  10. 2026-11-20 17:08 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  11. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.9% · 60th percentile
  12. 2026-11-20 16:27 UTCVendor advisory
  13. 2026-11-20 16:27 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  14. 2026-11-19 21:28 UTCEchelonGraph re-scored
  15. 2026-11-19 21:28 UTCVendor advisory
  16. 2026-11-19 21:28 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  17. 2026-11-19 20:43 UTCEchelonGraph re-scored
  18. 2026-11-19 20:43 UTCVendor advisory
  19. 2026-11-19 20:43 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  20. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  21. 2026-11-19 16:26 UTCVendor advisory
  22. 2026-11-19 16:26 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-11-19 11:48 UTCEchelonGraph re-scored
  24. 2026-11-19 11:48 UTCVendor advisory
  25. 2026-11-19 11:48 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
Show 32 more
  1. 2026-11-19 10:22 UTCEchelonGraph re-scored
  2. 2026-11-19 10:22 UTCVendor advisory
  3. 2026-11-19 10:22 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-11-18 21:28 UTCEchelonGraph re-scored
  5. 2026-11-18 21:28 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  6. 2026-11-18 20:58 UTCEchelonGraph re-scored
  7. 2026-11-18 20:58 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  8. 2026-11-18 20:28 UTCEchelonGraph re-scored
  9. 2026-11-18 20:28 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  10. 2026-11-18 20:14 UTCEchelonGraph re-scored
  11. 2026-11-18 20:13 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-11-18 19:29 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-11-18 16:43 UTCEchelonGraph re-scored
  14. 2026-11-18 16:43 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  15. 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.7% · 55th percentile
  16. 2026-11-18 16:25 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  17. 2026-11-18 13:48 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  18. 2026-11-18 05:28 UTCEchelonGraph re-scored
  19. 2026-11-18 05:28 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  20. 2026-11-18 04:53 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  21. 2026-11-18 04:20 UTCEchelonGraph re-scored
  22. 2026-11-18 04:20 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-11-18 02:29 UTCEchelonGraph re-scored
  24. 2026-11-18 02:28 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  25. 2026-11-18 02:14 UTCEchelonGraph re-scored
  26. 2026-11-18 02:14 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  27. 2026-11-18 00:48 UTCEchelonGraph re-scored
  28. 2026-11-18 00:48 UTCGHSA enrichmentGHSA-6g7j-4xh3-xq2q · GitHub severity HIGH · GitHub CVSS 8.1
  29. 2026-11-17 23:03 UTCENISA EUVD ID recordedEUVD-2026-127648 · Source: ENISA EUVD
  30. 2026-11-17 22:21 UTCEchelonGraph re-scored
  31. 2026-11-17 21:47 UTCEchelonGraph re-scoredFirst assessed: 8.1 HIGH
  32. 2026-11-17 21:43 UTCMITRE cvelistV5first tracked

Publicly available exploits

(13 references, 10 shown)

Public exploit code is referenced for this CVE (11 GitHub PoCs), as are 2 GitHub checker repositories. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.

  • GitHub PoCalt3kx/CVE-2026-114938
    Published Nov 19, 2026

    CVE-2026-114938 (Java4Shell) RCE PoC

    Open source ↗
  • GitHub PoCtc4dy/CVE-2026-114938-Toolkit
    Published Nov 19, 2026

    CVE-2026-114938 Java4Shell (CVSS 9.2) Base64 heap overflow Red/Blue toolkit. JDK/CPU exposure checks, bounded local proof, crash and mitigation tests, remote version scan, --profile heap hints, --persist/--exfil helpers, SOCKS5/Tor, stealth jitter, JSON reports. Experimental probe; experimental RCE chain. Only authorized security testing.

    Open source ↗
  • GitHub checkerMazeResearch/java4shell-check
    Published Nov 18, 2026

    Check your hosts, containers, images and AWS accounts for Java4Shell (CVE-2026-114938)

    Open source ↗
  • GitHub checkerzake1god/java2shell
    Published Nov 18, 2026

    Java4Shell (Java2Shell) CVE-2026-114938 local checker and vulnerable-vs-mitigated Docker lab

    Open source ↗
  • GitHub PoCboundaryx/cloudrasp-java4shell
    Published Nov 18, 2026

    Zero-downtime RASP hotpatch for CVE-2026-114938 (Java4Shell) — mirrors OpenJDK's official fix via live attach without restarting JVMs or disabling AVX-512 intrinsics.

    Open source ↗
  • GitHub PoCDungsocool/CVE-2026-114938
    Published Nov 18, 2026

    Java4Shell CVE-2026-114938 Analysis and Lab

    Open source ↗
  • GitHub PoCGhost-Bx1/java-exploits
    Published Nov 18, 2026

    OpenJDK / Java exploits - CVE-2026-114938 Java4Shell and more

    Open source ↗
  • GitHub PoCoflavioc/detect4shell
    Published Nov 18, 2026

    Java4Shell (CVE-2026-114938): kit de deteccao e prevencao defensiva, multi-engine. Seguranca Descomplicada.

    Open source ↗
  • GitHub PoCarturo-b-cmu/CVE-2026-114938
    Published Nov 17, 2026
    Open source ↗
  • GitHub PoCashrafzaryouh/CVE-2026-114938
    Published Nov 17, 2026

    CVE-2026-114938

    Open source ↗

Frequently asked(5)

What is CVE-2026-114938?
CVE-2026-114938 is a high-severity vulnerability; its CVE record was published on November 17, 2026. Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Compiler). Supported versions that are affected are Oracle Java SE: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3; Oracle GraalVM for JDK:…
When was the CVE record for CVE-2026-114938 published?
The CVE record for CVE-2026-114938 was published on November 17, 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 November 20, 2026; the record at its source may have been updated since.
Is CVE-2026-114938 actively exploited?
CVE-2026-114938 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-114938?
CVE-2026-114938 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending). EchelonGraph synthesises a secondary CVSS source + FIRST EPSS + GHSA into a combined EG score of 8.4 (HIGH).
How do I remediate CVE-2026-114938?
A fix for CVE-2026-114938 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-114938 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-114938?

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