dbcve.org
JreApplication · Oracle

CVE-2026-22021

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JSSE). Supported versions that are affected are Oracle Java SE: 8u481, 8u481-b50, 8u481-perf, 11.0.30, 17.0.18, 21.0.10, 25.0.2, 26; Oracle GraalVM for JDK: 17.0.18 and 21.0.10; Oracle GraalVM Enterprise Edition: 21.3.17. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTPS to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Note: This vulnerability can be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. This vulnerability also applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. CVSS 3.1 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Vulnerability in Oracle Java SE JSSE (Java Secure Socket Extension) component allows unauthenticated remote attackers with network access via HTTPS to cause partial denial of service. The vulnerability affects SSL/TLS handshake processing and can be exploited through web services using the JSSE APIs or via sandboxed Java Web Start applications/applets loading untrusted code.

MitigationApply the Oracle critical patch update (CPU) for the affected Java versions. For systems unable to patch immediately, restrict network exposure to Java applications and ensure sandbox restrictions are enforced for applet/Web Start deployments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JreApplication
Affected:= 1.8.0= 11.0.30= 17.0.18= 21.0.10= 25.0.2= 26
JdkApplication
Affected:= 1.8.0= 11.0.30= 17.0.18= 21.0.10= 25.0.2= 26
GraalvmApplication
Affected:= 21.3.17
Graalvm For JdkApplication
Affected:= 17.0.18= 21.0.10

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Java version
    Run 'java -version' (for JRE) or 'javac -version' (for JDK) from command line. Also check 'java -XshowSettings:properties -version' for detailed version info including 'java.version' property
    Affected if The displayed version matches any of the affected versions: 1.8.0, 11.0.30, 17.0.18, 21.0.10, 25.0.2, or 26 (for JRE/JDK); 21.3.17 (for GraalVM); 17.0.18 or 21.0.10 (for GraalVM for JDK)
  2. Confirm Java product type
    Run 'java -version' and check vendor string (Oracle, OpenJDK, etc). For GraalVM check 'java -version' or 'graalvm --version' to confirm GraalVM edition and version
    Affected if Product is Oracle JRE, Oracle JDK, Oracle GraalVM, or Oracle GraalVM for JDK with version matching the affected list
  3. Verify JSSE is in use
    Check if any Java application uses HTTPS connections. Inspect application configuration for javax.net.ssl properties, SSLContext.getInstance("TLS"), or HttpsURLConnection usage. Review application logs for JSSE handshake activity
    Affected if Any Java application using JSSE APIs for SSL/TLS communication via HTTPS is potentially affected since the vulnerability lies in SSL/TLS handshake processing within JSSE
  4. Check for Java Web Start or applet usage
    Search for JNLP files (.jnlp) on the system, check for Java Web Start configuration in registry (Windows) or application directories, review browser plugins or enterprise software that may load Java applets
    Affected if Java Web Start applications or Java applets that load untrusted code are present and executable on the system
  5. Assess network exposure
    Review firewall rules and network segmentation around systems running Java applications. Identify if Java services are exposed to untrusted networks or if they accept connections from external sources
    Affected if Java applications using JSSE are network-accessible from untrusted networks, increasing exploitation likelihood

Environment is affected if Oracle Java (JRE/JDK/GraalVM) matching the specific affected versions is installed AND the system runs network-accessible Java applications using HTTPS/JSSE or executes untrusted Java Web Start/applications

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Oracle critical patch update (CPU) for the affected Java versions. For systems unable to patch immediately, restrict network exposure to Java applications and ensure sandbox restrictions are enforced for applet/Web Start deployments.

Recommended fix High confidence

Oracle Java SE 8u491+, 11.0.31+, 17.0.19+, 21.0.11+, 25.0.3+, 26.0.1+; GraalVM for JDK 17.0.19+, 21.0.11+; GraalVM Enterprise Edition 21.3.18+

  1. 1. Identify the exact Oracle Java SE, GraalVM for JDK, or GraalVM Enterprise Edition version currently installed in your environment
  2. 2. For Oracle Java SE 8u481: upgrade to 8u491 or later
  3. 3. For Oracle Java SE 11.0.30: upgrade to 11.0.31 or later
  4. 4. For Oracle Java SE 17.0.18: upgrade to 17.0.19 or later
  5. 5. For Oracle Java SE 21.0.10: upgrade to 21.0.11 or later
  6. 6. For Oracle Java SE 25.0.2: upgrade to 25.0.3 or later
  7. 7. For Oracle Java SE 26: upgrade to 26.0.1 or later
  8. 8. For GraalVM for JDK 17.0.18: upgrade to 17.0.19 or later
Caveat Java major version upgrades (e.g., 17 to 21) may introduce breaking changes in application code and dependencies; test thoroughly before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jre Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22021 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22021 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data