CVE-2026-21932: Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of O...
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).
Security readout for executives and security teams
Plain-English summary
This flaw can let an unauthenticated remote attacker alter or destroy critical data when a user interacts with untrusted code in certain sandboxed Java client deployments. It primarily concerns Java Web Start applications and applets relying on the Java sandbox, not typical servers running only administrator-installed trusted code.
Executive priority
Prioritize affected user-facing Java clients that process untrusted code. Accelerate updates or isolation for those systems because successful exploitation can modify or delete critical data. Trusted-code-only servers are outside Oracle's stated applicability, so validate architecture before declaring broad enterprise exposure.
Technical view
CVE-2026-21932 affects AWT and JavaFX in specified Oracle Java SE and GraalVM releases. Exploitation is network-accessible, low complexity, requires no privileges, and needs user interaction. Successful exploitation can cross security scope and cause high-integrity impact without stated confidentiality or availability impact. CVSS 3.1: 7.4.
Likely exposure
Highest exposure exists where affected releases run sandboxed Java Web Start applications or applets that load untrusted internet-originated code. Oracle states the vulnerability does not apply to typical server deployments that load and run only trusted administrator-installed code.
Exploitation context
The supplied sources describe the vulnerability as easily exploitable but requiring interaction by someone other than the attacker. The CVE is not listed as KEV in the bundle, and no supplied evidence establishes active exploitation. Treat exploit activity as unconfirmed.
Researcher notes
The weakness is categorized as CWE-1287. The supplied material identifies AWT and JavaFX but does not provide root-cause details, proof-of-concept information, or confirmed exploitation. Assessment should focus on runtime version, trust boundary, sandbox reliance, content origin, and required user interaction without attempting production exploitation.
Mitigation direction
Identify affected Oracle Java SE and GraalVM versions across client environments.
Apply applicable Oracle CPU or downstream vendor security updates after compatibility testing.
Disable unnecessary Java Web Start, applet, or untrusted-code workflows.
Restrict untrusted network content from reaching remaining sandbox-dependent Java clients.
Validation and detection
Inventory runtime versions and distinguish client deployments from trusted-code-only servers.
Confirm whether Java Web Start, applets, AWT, or JavaFX process untrusted content.
Verify installed updates against Oracle or the relevant downstream vendor advisory.
Retest affected applications while ensuring sandbox-dependent untrusted workflows remain disabled or controlled.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1287: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1287 · source CWE mapping
Improper Validation of Specified Type of Input
Improper Validation of Specified Type of Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.