CVE-2026-21932: High severity Oracle Java SE vulnerability

Published Jan 15, 2026
·
Updated

Desktop.browse() will run a program if the URI is a filename while the documentation says that the default browser will be used to open the URI.

Other sources

Java SE could allow a remote attacker to bypass security controls and create, delete, or modify critical data or all accessible data, caused by an easily exploitable vulnerability.

IBM

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).

NVD

Affected Software

24 affected components
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, =21.0.9
Oracle GraalVM Enterprise Edition=21.3.16
Oracle GraalVM=21.3.16
Oracle GraalVM for JDK=17.0.17
Oracle GraalVM for JDK=21.0.9
Oracle JDK=1.8.0-update471
Oracle JDK=1.8.0-update471
Oracle JDK=1.8.0-update471_b50
Oracle JDK=11.0.29
Oracle JDK=17.0.17
Oracle JDK=21.0.9
Oracle JDK=25.0.1
Oracle JRE=1.8.0-update471
Oracle JRE=1.8.0-update471
Oracle JRE=1.8.0-update471_b50
Oracle JRE=11.0.29
Oracle JRE=17.0.17
Oracle JRE=21.0.9
Oracle JRE=25.0.1
IBM Controller<=11.0.1
IBM Controller<=11.1.0
IBM Controller<=11.1.1
IBM Controller<=11.1.2

Event History

Jan 15, 2026
Data Sourced
via Red Hat·12:04 PM
DescriptionSeverityAffected Software
Jan 20, 2026
CVE Published
via MITRE·09:56 PM
Data Sourced
via MITRE·09:56 PM
DescriptionSeverity
Data Sourced
via NVD·10:15 PM
DescriptionSeverityAffected Software
May 15, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-21932?

CVE-2026-21932 has a severity rating that indicates a significant risk due to its potential to execute arbitrary programs.

2

How do I fix CVE-2026-21932?

To address CVE-2026-21932, users should update to the latest patched version of Oracle Java SE or Oracle GraalVM as recommended by Oracle.

3

Which software versions are affected by CVE-2026-21932?

CVE-2026-21932 affects Oracle Java SE versions 8u471, 11.0.29, 17.0.17, 21.0.9, 25.0.1, and Oracle GraalVM versions 17.0.17, 21.0.9, and GraalVM Enterprise Edition 21.3.16.

4

What are the potential risks associated with CVE-2026-21932?

The risks of CVE-2026-21932 include unauthorized program execution, which can lead to data breaches or system compromise.

5

Is there a workaround for CVE-2026-21932?

Currently, the recommended action for CVE-2026-21932 is to apply available security updates, as no official workaround has been suggested.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203