CVE-2026-91375: Medium severity Oracle Java SE vulnerability
Vulnerability in Oracle Java SE (component: Libraries). Supported versions that are affected are Oracle Java SE: 8u503-perf, 11.0.32.1, 17.0.20.1, 21.0.12.1, 25.0.4.1, 27; Oracle GraalVM for JDK: 17.0.20.1 and 21.0.12.1; Oracle GraalVM Enterprise Edition: 21.3.19.1.1. Difficult to exploit vulnerability allows unauthenticated attacker with logon to the infrastructure where Oracle Java SE executes to compromise Oracle Java SE. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE accessible data. 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 4.7 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N).
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/openjdk-17to a version that resolves this vulnerability.Fixed in 17.0.21+9-1~deb12u1 - Upgrade
Upgrade
debian/openjdk-21to a version that resolves this vulnerability.Fixed in 21.0.13+9-1~deb13u2 - Upgrade
Upgrade
debian/openjdk-21to a version that resolves this vulnerability.Fixed in 21.0.13+9-1 - Upgrade
Upgrade
debian/openjdk-25to a version that resolves this vulnerability.Fixed in 25.0.5+8-1~deb13u1 - Upgrade
Upgrade
debian/openjdk-25to a version that resolves this vulnerability.Fixed in 25.0.5+8-1 - Upgrade
Upgrade
alpine/openjdk17to a version that resolves this vulnerability.Fixed in 17.0.21.0.3_p1-r0 - Upgrade
Upgrade
alpine/openjdk21to a version that resolves this vulnerability.Fixed in 21.0.13.0.3_p1-r0 - Upgrade
Upgrade
alpine/openjdk25to a version that resolves this vulnerability.Fixed in 25.0.5.0.3_p1-r0 - Upgrade
Upgrade
debian/openjdk-11to a version that resolves this vulnerability.Fixed in 11.0.33+9-1 - Upgrade
Upgrade
debian/openjdk-17to a version that resolves this vulnerability.Fixed in 17.0.21+9-1~deb12u1Fixed in 17.0.21.0.3+1-1 - Upgrade
Upgrade
debian/openjdk-21to a version that resolves this vulnerability.Fixed in 21.0.13+9-1~deb13u2Fixed in 21.0.13.0.3+1-1 - Upgrade
Upgrade
debian/openjdk-25to a version that resolves this vulnerability.Fixed in 25.0.5+8-1~deb13u1Fixed in 25.0.5+8-1Fixed in 25.0.5.0.3+1-1 - Upgrade
Upgrade
debian/openjdk-27to a version that resolves this vulnerability.Fixed in 27.0.1.0.3+1-1 - Upgrade
Upgrade
ubuntu/openjdk-ltsto a version that resolves this vulnerability.Fixed in 11.0.33+9-1ubuntu1~18.04.1 - Upgrade
Upgrade
ubuntu/openjdk-ltsto a version that resolves this vulnerability.Fixed in 11.0.33+9-1ubuntu1~20.04.1 - Upgrade
Upgrade
ubuntu/openjdk-25to a version that resolves this vulnerability.Fixed in 25.0.5.0.3+1-1~22.04.1 - Upgrade
Upgrade
ubuntu/openjdk-ltsto a version that resolves this vulnerability.Fixed in 11.0.33+9-1ubuntu1~22.04.1 - Upgrade
Upgrade
ubuntu/openjdk-25to a version that resolves this vulnerability.Fixed in 25.0.5.0.3+1-1~24.04.1 - Upgrade
Upgrade
ubuntu/openjdk-ltsto a version that resolves this vulnerability.Fixed in 11.0.33+9-1ubuntu1~24.04.1 - Upgrade
Upgrade
ubuntu/openjdk-25to a version that resolves this vulnerability.Fixed in 25.0.5.0.3+1-1~26.10.1 - Upgrade
Upgrade
ubuntu/openjdk-27to a version that resolves this vulnerability.Fixed in 27.0.1.0.3+1-1~26.10.1 - Upgrade
Upgrade
ubuntu/openjdk-ltsto a version that resolves this vulnerability.Fixed in 11.0.33+9-1ubuntu1~26.10.1 - Upgrade
Upgrade
ubuntu/openjdk-25to a version that resolves this vulnerability.Fixed in 25.0.5.0.3+1-1~26.04.1 - Upgrade
Upgrade
ubuntu/openjdk-ltsto a version that resolves this vulnerability.Fixed in 11.0.33+9-1ubuntu1~26.04.1
Event History
Frequently Asked Questions
Does an attacker need an Oracle Java SE account or elevated privileges to exploit this issue?
No privileges are required, but the attacker must have logon access to the infrastructure where Oracle Java SE is running. Exploitation is difficult and also requires interaction by someone other than the attacker.
Can a web service make this vulnerability reachable?
Yes. The issue can be exploited through APIs in the affected Libraries component, including when a web service supplies data to those APIs.
Which client-side Java deployments are specifically exposed?
Sandboxed Java Web Start applications and sandboxed Java applets are affected when they load and execute untrusted code, such as code obtained from the internet, while relying on the Java sandbox for security.