dbcve.org
JdkApplication · Oracle

CVE-2026-22013

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 →
60/100
Remediation priority · Elevated
Remotely reachable No privileges

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: JGSS). 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. 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 require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability 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. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N).

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 · high confidence

A vulnerability in the JGSS (Java Generic Security Services) component of Oracle Java SE and GraalVM allows unauthenticated attackers with network access to potentially access critical data. The flaw requires human interaction and only affects sandboxed Java Web Start applications or applets loading untrusted code, not server deployments running trusted code.

MitigationApply Oracle's available security patches for affected versions (8u481+, 11.0.30+, 17.0.18+, 21.0.10+, 25.0.2+, 26, or GraalVM equivalents). For server deployments running only trusted code, this vulnerability does not apply.

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
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
JreApplication
Affected:= 1.8.0= 11.0.30= 17.0.18= 21.0.10= 25.0.2= 26

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Determine installed Java version
    Run 'java -version' or 'java -fullversion' from the command line to get the exact version string
    Affected if The version matches one of the affected versions: 8u, 11.0.30, 17.0.18, 21.0.10, 25.0.2, 26, or GraalVM 21.3.17, or GraalVM for JDK 17.0.18 or 21.0.10
  2. Identify if running JDK or JRE
    Check whether the installation is Oracle JDK or Oracle JRE by examining the installation directory or running 'java -version' output which indicates JDK or JRE
    Affected if Affected only if running Oracle JDK or Oracle JRE matching the versions above; Oracle GraalVM and GraalVM for JDK are also affected
  3. Verify if Java Web Start or applets are in use
    Check for presence of javaws (Java Web Start) or applet configurations in the environment, or check if applications are being launched via JNLP files
    Affected if Only affected if Java Web Start applications or applets loading untrusted code are being executed; if no Web Start or applets are used, the vulnerability does not apply
  4. Confirm deployment context
    Determine if this is a server-side deployment running only trusted code or a client-side environment with sandboxed untrusted code execution
    Affected if Server deployments running only trusted code are NOT affected by this vulnerability; it only affects sandboxed environments loading untrusted code

A user is affected only if they are running an affected JDK/JRE/GraalVM version AND using Java Web Start or applets to load untrusted code in a sandboxed environment, not server deployments with trusted code only.

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 Oracle's available security patches for affected versions (8u481+, 11.0.30+, 17.0.18+, 21.0.10+, 25.0.2+, 26, or GraalVM equivalents). For server deployments running only trusted code, this vulnerability does not apply.

Recommended fix Moderate confidence

Oracle Java SE 8u511+/11.0.25+/17.0.11+/21.0.5+ or Oracle GraalVM for JDK 17.0.19+/21.0.11+

  1. 1. Identify the exact Java/JDK version currently installed using `java -version` or checking the JRE/JDK installation directory.
  2. 2. Download the latest Oracle Java SE CPU (Critical Patch Update) that addresses this vulnerability from Oracle's official website (www.oracle.com/java/technies/downloads/).
  3. 3. For Oracle Java SE 8: Upgrade to a version higher than 8u481 (e.g., 8u511 or later).
  4. 4. For Oracle Java SE 11: Upgrade to a version higher than 11.0.30 (e.g., 11.0.25 or later CPU).
  5. 5. For Oracle Java SE 17: Upgrade to a version higher than 17.0.18 (e.g., 17.0.11 or later).
  6. 6. For Oracle Java SE 21: Upgrade to a version higher than 21.0.10 (e.g., 21.0.5 or later).
  7. 7. For Oracle GraalVM for JDK 17: Upgrade to a version higher than 17.0.18.
  8. 8. For Oracle GraalVM for JDK 21: Upgrade to a version higher than 21.0.10.
Caveat Major version upgrades (e.g., Java 8 to 17/21) may introduce breaking changes in application code, APIs, or removed features; test thoroughly before production deployment

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

Fix this in Jdk Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22013 — 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-22013 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