Java4Shell:Java 17 中的预认证远程代码执行漏洞危及服务器 (CVE-2026-114938)
Java4Shell: pre-auth RCE flaw in Java 17 puts servers at risk (CVE-2026-114938)

原始链接: https://www.aikido.dev/blog/java-17-rce-vulnerability-cve-2026-114938

Java4Shell(CVE-2026-114938)是一个报告称存在于 Java 17 中的未经身份验证的远程代码执行漏洞,CVSS 4.0 评分为 9.2。Oracle 于 2026 年 11 月 17 日发布修补版本,影响 Java SE 8、11、17、21、25 和 27,以及 Oracle GraalVM、JavaFX、其他 OpenJDK 供应商、Linux 软件包、捆绑 JDK 和容器基础镜像。用户应将每个 Java 版本更新到 Oracle 或其供应商列出的修补版本。受影响的 Oracle 版本包括 8u511、11.0.33、17.0.21、21.0.13、25.0.5 和 27.0.1;修补版本为 8u513、11.0.33.1、17.0.21.1、21.0.13.1、25.0.5.1 和 27.0.1.1。截至 11 月 17 日,未报告野外利用,但技术细节可能随后公布,因此请尽快修补。Aikido 的“Am I affected?”工具可以检查环境。

Hacker News 的一个讨论线程讨论了“Java4Shell”(CVE-2026-114938),被描述为 Java 17 中的一个预认证 RCE 漏洞。评论者分享了未经验证的细节,包括 AMD64 上可能的 AVX512/Base64 解码问题,以及诸如 -XX:UseAVX=2 或禁用 Base64 内在函数之类的建议 workaround。攻击向量和受影响用法仍不明确,尽管消息来源指向 HotSpot/编译器参与。补丁链接和发布说明被分享。一些评论者质疑它是否真正的远程代码执行还是拒绝服务,而另一些人认为它可能是一个复杂的内存 bug,并敦促在不恐慌的情况下打补丁。总体而言,细节仍在浮现,尚未完全验证。
相关文章

原文

TL;DR

  • Calif has disclosed Java4Shell (CVE-2026-114938), a reported unauthenticated remote code execution flaw in Java 17, rated 9.2 under CVSS 4.0.
  • Oracle released patched builds on November 17, 2026. It lists Java SE 8, 11, 17, 21, 25 and 27 as affected by its November update.
  • Update every Java line you run to the patched build in the table below.‍
  • To find out if you are affected, click "Am I affected?" on the Aikido dashboard.

Which Java versions and builds are affected?

Oracle's pre-release announcement lists these builds as affected by the vulnerabilities in the November update:

All Java builds Oracle lists as affected (Oracle pre-release announcement), with the patched builds from Oracle's November 17, 2026 release notes.
Product Affected build (Oracle) Patched build (November 17 update)
Oracle Java SE 8 8u511, 8u511-perf 8u513
Oracle Java SE 11 11.0.33 11.0.33.1
Oracle Java SE 17 17.0.21 17.0.21.1
Oracle Java SE 21 21.0.13 21.0.13.1
Oracle Java SE 25 25.0.5 25.0.5.1
Oracle Java SE 27 27.0.1 27.0.1.1
Oracle GraalVM for JDK 17.0.21, 21.0.13 Not listed
Oracle GraalVM Enterprise Edition 21.3.20.0.3 Not listed
Oracle JavaFX 21.0.13, 25.0.5, 27.0.1 Not listed

Java builds to check:

  • Oracle Java SE (JDK and JRE)
  • Oracle GraalVM for JDK and GraalVM Enterprise Edition
  • Oracle JavaFX
  • OpenJDK builds from other vendors, such as Eclipse Temurin, Amazon Corretto, Azul Zulu, the Microsoft Build of OpenJDK and the Red Hat build of OpenJDK
  • Linux distribution packages such as openjdk-17
  • JDKs bundled inside applications and container base images

How to fix Java4Shell

  • Update to the patched build for your Java line. Use the table above.
  • Use your vendor's fixed build. If you run Temurin, Corretto, Zulu or a distribution package, wait for that vendor's fixed version, which may carry a different build number.
  • Not sure where you run Java? See the next section.

Am I affected by Java4Shell?

  • You are in scope if you run any Java line in the table above. That includes bundled JDKs and container base images.
  • To find out if you are affected, click "Am I affected?" on the Aikido home page. It checks your environment for this vulnerability, so you do not need to track down every Java runtime by hand.
  • Start with internet-facing services. Anything reachable from outside is the likeliest to be hit once details are public.

What is Java4Shell (CVE-2026-114938)?

Java4Shell is the name Calif, the firm that discovered and reported the flaw, has given CVE-2026-114938. Early reports describe it as an unauthenticated remote code execution flaw in OpenJDK 17.0.6 and later, rated 9.2 (Critical) under CVSS 4.0. Oracle scores Java flaws under CVSS 3.1, where its highest Java SE score this month is 8.1, so the two figures may describe different issues. For reference, 9.2 under CVSS 4.0 is the same score PHP2Shell carries.

Calif has said it will publish technical details after Oracle's patch release. Until then, the vulnerable component and the conditions for exploitation are not public. We will update this post when they are.

Is Java4Shell being exploited?

As of November 17, we have seen no reports of exploitation in the wild. Calif's technical details are due later today, and exploitation can follow quickly once details are public, so patch now. We will update this post if that changes.

FAQ

What is Java4Shell? The name Calif has given CVE-2026-114938, a reported unauthenticated remote code execution flaw in Java 17 rated 9.2 under CVSS 4.0.

Which Java versions are affected? Reports name OpenJDK 17.0.6 and later. Oracle lists Java SE 8, 11, 17, 21, 25 and 27 as affected by its November update.

Has Oracle released a patch? Yes. Oracle released patched builds on November 17, 2026. They are listed in the table above. OpenJDK vendors ship on their own schedules.

Is Java4Shell being exploited? We have seen no reports of exploitation as of November 17.

Is there a workaround? None has been published that we are aware of. Patching is the fix.

How do I know if I am affected? Click "Am I affected?" on the Aikido home page.

‍

联系我们 contact @ memedata.com