CVE-2026-114938: Reported Critical Pre-authentication Remote Code Execution in Java 17
CVE-2026-114938: Critical pre-authentication RCE in Java 17 reported.
A critical memory corruption vulnerability, CVE-2026-114938, has been reported in Java 17 and above, potentially allowing unauthenticated remote code execution. The reported severity is Critical with a CVSSv4 score of 9.2, though details are preliminary pending official advisories from Oracle or OpenJDK. Rapid7 is monitoring the situation and has provided vulnerability checks for its customers.
AI summary of the linked source. Not reviewed by an editor. How this works
Run Oracle?
Get an email when a new story names Oracle, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonA critical memory corruption vulnerability (CVE-2026-114938) has been reported affecting Java 17 and above, carrying a CVSSv4 score of 9.2 and enabling unauthenticated remote code execution — meaning attackers need no credentials to compromise exposed systems. The root issue lies in a flaw within the Java runtime itself, underscoring how foundational platform components can become systemic risks across entire application estates. Because Java underpins countless enterprise applications, APIs, and middleware, a single unpatched runtime vulnerability can expose an enormous attack surface simultaneously. The preliminary nature of the advisory also highlights the importance of continuous vulnerability intelligence monitoring, so organizations can act before official patches arrive.
What helps against this
How we list vendors- Vulnerability scanning and prioritisation
You know which systems are vulnerable, and which ones to fix first.
- Automated patch management
Known holes get closed in days, not months.
- Threat intelligence
Attack campaigns reach your sector, suppliers or software before your team hears about them.
Indicators of Compromise
Addresses and file hashes are copied from the publisher's page by pattern matching. Names are picked by AI. On stories from before 17 November 2026, some addresses and hashes were picked by AI too. Not reviewed by an editor. How this works
- cve: CVE-2026-114938