deniz.in

Markets

Weather

Loading weather

· via Hacker News – Front Page (native)

Oracle ships Java fixes for reported Java4Shell pre-auth RCE (CVE-2026-114938)

Oracle has released patched builds for Java4Shell, a reported unauthenticated RCE in Java that researcher Calif scored 9.2 under CVSS 4.0, with Java SE 8 through 27 listed as affected.

Oracle ships Java fixes for reported Java4Shell pre-auth RCE (CVE-2026-114938)

A critical rating and same-day patches

Security firm Calif, which discovered and reported the flaw, has disclosed a vulnerability it calls Java4Shell, tracked as CVE-2026-114938 and described as an unauthenticated remote code execution flaw in Java 17. According to Aikido, which published a write-up on the disclosure, the bug carries a 9.2 rating (Critical) under CVSS 4.0. Oracle released patched builds for every affected Java release line on November 17, 2026, the same day the disclosure became public, which makes updating the practical response rather than waiting on further analysis.

Which versions and builds are affected

Aikido reports that Oracle's November update lists six Java SE release lines as affected, with these patched builds now available:

  • Oracle Java SE 8: affected 8u511 and 8u511-perf, fixed in 8u513
  • Oracle Java SE 11: affected 11.0.33, fixed in 11.0.33.1
  • Oracle Java SE 17: affected 17.0.21, fixed in 17.0.21.1
  • Oracle Java SE 21: affected 21.0.13, fixed in 21.0.13.1
  • Oracle Java SE 25: affected 25.0.5, fixed in 25.0.5.1
  • Oracle Java SE 27: affected 27.0.1, fixed in 27.0.1.1

Oracle also lists GraalVM for JDK (17.0.21 and 21.0.13), GraalVM Enterprise Edition (21.3.20.0.3) and JavaFX (21.0.13, 25.0.5 and 27.0.1) as affected, but Aikido notes that no patched builds were listed for those products in the release notes.

The scope of the flaw is not fully settled. Calif's early reports describe the vulnerability as affecting OpenJDK 17.0.6 and later, while Oracle's affected list spans Java 8 through Java 27. Aikido also flags a scoring discrepancy: Oracle rates its Java flaws under CVSS 3.1, where its highest Java SE score this month is 8.1, so Calif's 9.2 CVSS 4.0 figure and Oracle's numbers may not describe the same issue.

Where vulnerable runtimes tend to hide

Per Aikido, the builds to check include Oracle's JDK and JRE distributions, both GraalVM editions, JavaFX, and OpenJDK builds from vendors such as Eclipse Temurin, Amazon Corretto, Azul Zulu, the Microsoft Build of OpenJDK and the Red Hat build. Linux distribution packages like openjdk-17 are also in scope, as are JDKs bundled inside applications and container base images, which are frequently the copies operators forget about.

For non-Oracle distributions, fixes arrive on each vendor's own schedule and may carry different build numbers, so Aikido recommends tracking your vendor's fixed release rather than relying on Oracle's numbering.

What is still unknown

The technical details have not been published. Calif said it would release them after Oracle's patch shipped, and as of November 17 the vulnerable component and the conditions required for exploitation were still private, according to Aikido.

Two other open questions remain. There were no reports of exploitation in the wild as of November 17, and no workaround has been published, so patching is currently the only fix. Aikido's practical guidance is to start with services reachable from the internet, which it calls the likeliest targets once details become public.

Why it matters

An unauthenticated remote code execution flaw in the Java runtime itself would apply to essentially every Java service that exposes a network interface, and Java remains one of the most widely deployed server runtimes in enterprise environments. The timing is what makes this urgent: Oracle's patches are out, but Aikido reports that Calif's technical write-up was expected the same day, and attacks often begin soon after such details surface. Fleets that get their Java from base images, bundled JDKs or distribution packages will need to hunt down every copy, not just the obvious installs, and older lines like Java 8 and 11 are still common in production. The gap between a fixed build and a weaponized exploit is, on this story's own timeline, short.

  • #java
  • #security
  • #openjdk
  • #oracle
  • #vulnerability-management

Related posts