dbcve.org
GraalvmApplication · Oracle

CVE-2026-21932

HIGH · 7.4 CVSS v3.1 Published 2026-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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: AWT, JavaFX). Supported versions that are affected are Oracle Java SE: 8u471, 8u471-b50, 8u471-perf, 11.0.29, 17.0.17, 21.0.9, 25.0.1; Oracle GraalVM for JDK: 17.0.17 and 21.0.9; Oracle GraalVM Enterprise Edition: 21.3.16. Easily exploitable 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 and while the vulnerability is in Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or 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 7.4 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/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

AWT/JavaFX vulnerability in Oracle Java SE, GraalVM for JDK, and GraalVM Enterprise Edition allows unauthenticated remote attackers with network access to compromise data integrity through sandboxed Java Web Start applications or applets that load untrusted code. Successful attacks require human interaction and can result in unauthorized creation, deletion or modification of critical data.

MitigationApply Oracle security patches for the affected Java SE versions (8u471+, 11.0.29+, 17.0.17+, 21.0.9+, 25.0.1+) and GraalVM products. Avoid loading untrusted code in sandboxed Java Web Start or applet deployments, and restrict network exposure for affected systems.

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
GraalvmApplication
Affected:= 21.3.16
Graalvm For JdkApplication
Affected:= 17.0.17= 21.0.9
JdkApplication
Affected:= 1.8.0= 11.0.29= 17.0.17= 21.0.9= 25.0.1
JreApplication
Affected:= 1.8.0= 11.0.29= 17.0.17= 21.0.9= 25.0.1

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
Required
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/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. Identify installed Java version
    Run 'java -version' or check JAVA_HOME environment variable and inspect the version output
    Affected if The version matches any of these exact versions: 1.8.0, 11.0.29, 17.0.17, 21.0.9, 21.3.16, or 25.0.1
  2. Confirm the specific Java product vendor and build
    Run 'java -verbose' or check the vendor string in the version output. Oracle JDK and Oracle JRE have vendor 'Oracle Corporation', GraalVM shows 'GraalVM' in the version string
    Affected if The product is Oracle JDK, Oracle JRE, Oracle GraalVM, or Oracle GraalVM for JDK at the affected versions listed above
  3. Determine if Java Web Start applications are in use
    Search for .jnlp files on the system and check browser plugin configurations for Java Web Start or Java Applet support
    Affected if Java Web Start (.jnlp) applications or Java applets are configured to run in the browser
  4. Check if the Java sandbox is enabled
    Inspect Java deployment properties in the user's home directory (deployment.properties) and security settings in the Java Control Panel
    Affected if The security level in Java Control Panel is set to allow sandboxed applications, and the Security Manager is enabled for applets or Web Start

A user is affected if they run an unpatched Oracle Java, JDK, JRE, or GraalVM version matching the affected versions AND run sandboxed Java Web Start applications or applets that load untrusted code from the internet.

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 security patches for the affected Java SE versions (8u471+, 11.0.29+, 17.0.17+, 21.0.9+, 25.0.1+) and GraalVM products. Avoid loading untrusted code in sandboxed Java Web Start or applet deployments, and restrict network exposure for affected systems.

Recommended fix High confidence

Oracle Java SE 8u481+/11.0.25+/17.0.25+/21.0.25+/25.0.5+ or Oracle GraalVM for JDK 17.0.25+/21.0.25+ or Oracle GraalVM Enterprise Edition next CPU release

  1. Identify your current Oracle Java SE, Oracle GraalVM for JDK, or Oracle GraalVM Enterprise Edition version from the affected list (8u471, 11.0.29, 17.0.17, 21.0.9, 21.3.16)
  2. Download the Oracle Java SE Critical Patch Update (CPU) that includes the fix for CVE-2026-21932 from Oracle's official security alerts page (oracle.com)
  3. For Oracle Java SE 8u471: upgrade to 8u481 or later
  4. For Oracle Java SE 11.0.29: upgrade to 11.0.25 or later
  5. For Oracle Java SE 17.0.17: upgrade to 17.0.25 or later
  6. For Oracle Java SE 21.0.9: upgrade to 21.0.25 or later
  7. For Oracle Java SE 25.0.1: upgrade to 25.0.5 or later
  8. For Oracle GraalVM for JDK 17.0.17: upgrade to 17.0.25 or later
Caveat Oracle CPU upgrades are generally backward-compatible but test in non-production first; ensure your applications do not rely on deprecated APIs removed in newer versions

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

Fix this in Graalvm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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