Critical Java 17 RCE Vulnerability Puts Servers at Risk as Oracle Releases 11 Security Fixes
What happened?
A remote code execution (RCE) vulnerability in Java 17 has prompted warnings for server admins, especially as Oracle released 11 new Java SE security updates on the same day. The bug is tracked as CVE-2026-114938. Public reports say it needs no login and affects OpenJDK 17.0.6 and later. The details are still unconfirmed. Security firm watchTowr said on X that it is aware of public reports of an unauthenticated RCE in Java. It told teams to review their Java environments and watch for vendor news. Reports rate the flaw 9.2 out of 10 under CVSS 4.0, which is Critical.
Key details
- Security firm watchTowr confirmed awareness of public reports of an unauthenticated RCE in Java.
- South Korea's National Intelligence Service warned public bodies about a Java flaw allowing unauthenticated remote code execution.
- The CVE record remains reserved with no public description and no fixed build or proof-of-concept published.
- Oracle's November 2026 Critical Security Patch Update includes 11 Java SE fixes, all exploitable over a network without credentials.
- Oracle lists affected builds including Java SE 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 and 27.0.1 but has not tied any fix to CVE-2026-114938.
- Java 17 is a long-term support release widely used in banks, cloud services and back-end systems since January 2023.
What is affected?
- OpenJDK 17 versions 17.0.6 and later
- Oracle Java SE 8u511, 8u511-perf
- Oracle GraalVM for JDK 17.0.21, 21.0.13
- Oracle GraalVM Enterprise Edition 21.3.20.0.3
- Oracle JavaFX 21.0.13, 25.0.5, 27.0.1
Summarised by SecOraLens from Cyber Security News. Always read the original source before acting. How SecOraLens verifies advisories.
What to do next
Brief your board. Brief your team.
Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.
