Oracle has shipped a Java security update fixing CVE-2026-114938, a memory corruption flaw in Java 17 and later that can, in some cases, let a remote attacker run code on a server without logging in. The bug carries a CVSS 4.0 score of 9.2, rated Critical.
AhnLab's ASEC team, which published patch guidance after Oracle's release at 6:00 a.m. Korea Standard Time on November 17, lists every supported long-term branch from Java 17 onward as affected. Rapid7 also flagged the flaw in an emergent threat response note, cautioning that the CVE-specific details remained preliminary pending confirmation in Oracle and OpenJDK advisories.
Java runs underneath a large share of enterprise back-end software, so a critical bug that needs no authentication puts internet-facing Java services at the top of the patch queue. It is also the second Java fix of this severity in under a month, after Oracle's out-of-band patch for a 9.1-rated flaw in October.
Every branch from Java 17 up is in scope
According to AhnLab, the affected builds are:
- Java 17: 17.0.21.0.3 and earlier
- Java 21: 21.0.13.0.3 and earlier
- Java 25: 25.0.5.0.3 and earlier
- Java 27: 27.0.1.0.3 and earlier
Neither AhnLab nor Rapid7 has described how the memory corruption is triggered, which Java component contains it, or what an attacker would need to reach. Rapid7 noted that the reported details could still change, and Oracle's November security alert is the authoritative source for the technical detail. Neither company reported exploitation in the wild at the time of writing, and neither mentioned a public proof of concept.
Update to the 1+4 builds, then restart services
AhnLab recommends moving each major version to its fixed build:
- Java 17: 17.0.21.1+4
- Java 21: 21.0.13.1+4
- Java 25: 25.0.5.1+4
- Java 27: 27.0.1.1+4
To find out which runtime a host is using, locate the binary (where.exe java on Windows, which java on Linux), then run java -version from that path. Servers often carry more than one runtime, and many applications ship their own bundled Java, so check each install rather than the system default alone. After updating, restart the services that use Java and confirm the new version is the one actually running in production.
Until the patch is in place, AhnLab advises monitoring internet-exposed services and cutting unnecessary external access to them. Rapid7 customers can check exposure with an authenticated vulnerability check shipped in its November 17 content release (1.1.4115).
A critical, unauthenticated bug in a runtime this widespread is the kind of patch attackers study closely, even before anyone publishes a working exploit. Treat this one as an emergency change, not an item for the next quarterly patch cycle.
This briefing is provided by IntelFusions for informational and defensive purposes only. It is based on sources assessed to be reliable at the time of writing, and analytic judgments carry the confidence levels indicated. Indicators of compromise are defanged; re-arm them only in controlled environments. IntelFusions is not affiliated with the organizations named and makes no warranty as to completeness or accuracy.