Skip to main content
株式会社オブライト
株式会社オブライト

Java4Shell CVE-2026-114938 + 5 more

Vulnerability Digest Nov 18, 2026

Published 2026/11/1811 min read

Java4Shell (CVE-2026-114938, CVSS 8.1): update Java today or add -XX:-UseBASE64Intrinsics. Puppet Enterprise CVE-2026-115731 exploited. OpenSSL, Chrome too.

From the information published on Nov 17-18, we picked the items most relevant to small-business systems. The top priority is Java4Shell in Java (OpenJDK), CVE-2026-114938 (CVSS v3.1 8.1). A memory-corruption flaw in Java's Base64 decoding, which the discoverer says allowed unauthenticated remote code execution on Keycloak, Jira, Confluence, Jenkins and others. A proof-of-concept is public. Check whether Java runs on your servers and your vendors' servers, and update to your distribution's latest fixed build today. If you cannot update right away, a startup option works around it. As of Nov 18, JPCERT/CC has not confirmed exploitation in real attacks.

Next is Puppet Enterprise CVE-2026-115731 (CVSS v3.1 9.9 in NVD), added by CISA to its KEV catalog on Nov 17 (due Dec 1). If you manage servers with Puppet, check your version. We also cover the OpenSSL advisory (three Low issues; fixed releases are scheduled for Dec 1) and the Google Chrome 158 security update (204 fixes). In this digest, "exploitation confirmed" means listed in CISA KEV or stated as exploited by the vendor or another primary source. Today one item has confirmed exploitation (Puppet Enterprise).

Today's vulnerabilities at a glance

ProductCVESeverity (CVSS)ExploitationFix
Java (OpenJDK, Oracle Java SE, etc.)CVE-2026-114938 (Java4Shell)8.1 (v3.1, OpenJDK and Oracle); the discoverer rates it 9.2 on v4.0Not confirmed; PoC public (JPCERT/CC, as of Nov 18)Update to each vendor's latest fixed build; workaround -XX:-UseBASE64Intrinsics
Puppet Enterprise (Perforce)CVE-2026-1157319.9 (NVD v3.1), 9.4 (vendor v4.0)Confirmed (added to CISA KEV Nov 17)2023.8.13 / 2025.12.1 / 2026.0.1 or later
OpenSSLCVE-2026-107493Low (OpenSSL rating)None notedFixed releases scheduled Dec 1 (4.1.1 / 4.0.4 / 3.5.10 etc.)
OpenSSLCVE-2026-124709Low (same)None notedSame (4.1.1 / 4.0.4 / 3.5.10)
OpenSSLCVE-2026-35190Low (same)None notedSame (4.1.1 / 4.0.4 / 3.5.10)
Google Chrome (desktop)204 fixes (6 Critical)Critical, High and others (Chromium rating)None noted158.0.8127.36 or later (.36/.37 on Windows and Mac)

Java (OpenJDK) Java4Shell CVE-2026-114938: unauthenticated code execution possible via Base64 acceleration

What happens. To speed up Base64 conversion, Java has dedicated code that uses certain CPU instructions (AVX-512 VBMI). The part that handles the last few characters has a flaw, and a crafted string causes a write to an unintended place in memory. JPCERT/CC says it can lead to theft of sensitive information or arbitrary code execution. The discoverer, Calif, reports unauthenticated remote code execution on Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate in default configurations. Base64 is widely used for authentication and file uploads, so Java applications in general may be exposed.

Severity. OpenJDK and Oracle rate it CVSS v3.1 8.1 (High), with attack complexity marked High. Calif rates it 9.2 (Critical) on CVSS 4.0; that is the discoverer's own rating.

Affected versions. OpenJDK lists 27.0.1.0.3, 25.0.5.0.3, 21.0.13.0.3, 17.0.21.0.3 and earlier (the risk matrix marks the 17, 21, 25 and 27 lines). Oracle lists Oracle Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3, and GraalVM Enterprise Edition 21.3.20.0.3. According to JPCERT/CC, OpenJDK-based products such as Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK may also be affected. Exploitation requires an x86-64 CPU with AVX-512 VBMI; ARM64 is reported as not affected. Products that bundle Java (business packages, for example) may be affected too.

Fix and workaround. OpenJDK and Oracle published fixes on Nov 17. We could not read the exact fixed version numbers from the Oracle or OpenJDK pages within our verification, so we do not state them here. Check your distribution's official page (Oracle, Corretto, Temurin, Microsoft, Red Hat, etc.) to confirm you are on a build released on or after Nov 17. If you cannot update right away, Calif and JPCERT/CC give two workarounds: add either of the following to the Java startup options.

# Disable the Base64 acceleration itself
-XX:-UseBASE64Intrinsics

# Disable AVX-512 (x86-64 only; fails to start on ARM)
-XX:UseAVX=2

Both may affect Java performance or behavior, so test them in a staging environment first. Add the option to each application's startup settings (such as JAVA_OPTS for Tomcat, Jenkins or Keycloak); the method differs by product.

How to check. Run the commands below on the server to see the Java version and vendor. On Linux, the second command shows whether the CPU supports AVX-512 VBMI (any output means supported).

java -version

# Linux: check AVX-512 VBMI support
grep -o 'avx512_vbmi' /proc/cpuinfo | sort -u

Servers with unsupported CPUs or on ARM do not meet the exploitation conditions, but you should still update. On cloud virtual machines the CPU type is hard to see, so updating Java and applying the workaround is more reliable than checking the CPU. For products that bundle Java, check the product vendor's information and wait for their update.

The same OpenJDK advisory also lists nine more CVEs, CVE-2026-114939 to 114947 (CVSS 3.7 to 7.4), and OpenJFX CVE-2026-86144 (7.5). Updating Java addresses them together.

Puppet Enterprise CVE-2026-115731: one certificate is enough to run code on the Puppet server

What happens. Puppet is a tool that manages the configuration of many servers at once. Managed machines (agents) send their run results to Puppet Server as "reports." The report-processing code has a flaw: anyone holding even one agent certificate signed by the CA can submit a crafted report and execute arbitrary code on Puppet Server as its service user. The CVE description adds that where the CA autosigns requests without strong verification, an unauthenticated network attacker can obtain a certificate as well.

Severity and exploitation. NVD rates it CVSS v3.1 9.9 (Critical); the vendor (Perforce) rates it 9.4 on v4.0. CISA added it to KEV on Nov 17 with a Dec 1 due date, and lists ransomware use as "Unknown." The CVE was entered in NVD on Nov 3, so exploitation was confirmed about two weeks later.

Affected and fixed versions. The CVE record lists Puppet Enterprise 2023.8.0 up to (not including) 2023.8.13, 2025.0.0 up to 2025.12.1, and 2026.0.0 up to 2026.0.1. The fixed versions are 2023.8.13, 2025.12.1 and 2026.0.1, all of which bundle puppet-agent 8.22.2 or 9.1.3. The vendor says to restart puppet server after upgrading so the fixed code is loaded. The record lists Puppet Enterprise only; we could not determine the status of open-source Puppet within our verification, so check Perforce's information if you use it.

How to check and respond. You can see the Puppet Enterprise version in the console or with a command on the server. The commands below are examples and vary by environment. Until you update, review your autosign settings and check for unfamiliar certificate requests or signed certificates. If external PUT requests can reach Puppet Server, consider restricting them at the network level. Because it is in KEV, and a compromised configuration server can spread to every managed server, prioritize the update.

# Puppet Enterprise version (example)
cat /opt/puppetlabs/server/pe_version

# Agent version (fixed releases bundle 8.22.2 or 9.1.3)
puppet --version

Official information: Perforce advisory, NVD, CISA KEV catalog.

OpenSSL CVE-2026-107493, CVE-2026-124709 and CVE-2026-35190: all Low, fixes due Dec 1

OpenSSL published three security advisories on Nov 17. OpenSSL rates all of them Low. The fixes are in the GitHub repository, but the releases containing them are scheduled for Dec 1 and are not out yet. Today, the thing to do is check whether you use the affected patterns.

CVEIssueAffected linesCondition
CVE-2026-107493Use-after-free in PEM_X509_INFO_read_bio_ex() after a failed read4.1, 4.0, 3.5, 3.0, 1.1.1, 1.0.2Only if the application passes a non-NULL stack. OpenSSL itself does not
CVE-2026-124709A QUIC server keeps state for rejected streams for the whole connection, so memory grows (denial of service)4.1, 4.0, 3.5If you run a QUIC server; reachable in the default configuration. About 300 bytes per stream, so growth is slow
CVE-2026-35190Out-of-bounds read in TLS 1.3 key-share processing (possible denial of service)4.1, 4.0, 3.5Only if the Suite B certificate flag is set with SSL_CTX_set_cert_flags() and TLS 1.3 is enabled; not reached by default

Fixed versions (scheduled) are 4.1.1 for 4.1, 4.0.4 for 4.0, and 3.5.10 for 3.5. For 3.0, 1.1.1 and 1.0.2, only CVE-2026-107493 applies, and the fixed versions (3.0.24, 1.1.1zk, 1.0.2zt) are for premium support customers. OpenSSL says 3.1, 3.2, 3.3, 3.4 and 3.6 are out of support and were not analyzed. Most small businesses receive OpenSSL through OS or middleware updates, so the regular update is enough. To check, run openssl version (if an application bundles its own copy, check that application's information).

openssl version

Google Chrome 158: 204 security fixes (6 Critical), no exploitation noted

On Nov 17, Google released Chrome 158 to the desktop stable channel. The version is 158.0.8127.36 (Linux) and 158.0.8127.36/.37 (Windows and Mac), with 204 security fixes. Six are Critical (CVE-2026-130963, CVE-2026-131031, CVE-2026-131060, CVE-2026-131008, CVE-2026-131054, CVE-2026-130975). The announcement does not state that an exploit exists in the wild. Rollout is gradual, so checking for updates manually applies it sooner. The Extended Stable channel also moved to 156.0.8078.108/.109 with 79 fixes.

To check, type chrome://settings/help in the address bar and confirm the version. If an update is available it downloads automatically; click Relaunch. If an administrator manages your company PCs centrally, ask them about the rollout. Other Chromium-based browsers (such as Edge) need to wait for their own updates.

Checklist for non-IT staff: what to do today

- Ask your vendors and maintenance contractors whether any systems run on Java (Keycloak, Jira, Confluence, Jenkins, Tomcat, etc.) and whether Java has been updated. If it cannot be updated, ask them to apply the startup option -XX:-UseBASE64Intrinsics
- If you use business software that bundles Java, check the developer's update information
- If you use Puppet Enterprise, confirm the version is 2023.8.13, 2025.12.1 or 2026.0.1 or later and restart puppet server after updating. If you do not use it, record it as not applicable
- For OpenSSL, wait for the Dec 1 fixed releases. Unless you use special setups (a QUIC server or Suite B settings), the regular update is enough
- On company PCs, open Chrome, go to chrome://settings/help, update to the 158 line and relaunch
- If none apply, record "not applicable" and you are done

Related articles

For preparing against vulnerabilities, see Vulnerability assessment costs and how to choose. For the previous day's information, see the Nov 17 vulnerability digest (WP Duplicate and more).

Sources

- OpenJDK Vulnerability Advisory 2026/11/17: https://openjdk.org/groups/vulnerability/advisories/2026-11-17
- Oracle Critical Security Patch Update Advisory - November 2026: https://www.oracle.com/security-alerts/cspunov2026.html
- JPCERT/CC CyberNewsFlash (CVE-2026-114938): https://www.jpcert.or.jp/newsflash/2026111801.html
- JVN#99608534: https://jvn.jp/vu/JVNVU99608534/
- Calif, "Java4Shell" (discoverer's disclosure): https://calif.io/java4shell/
- NVD CVE-2026-114938: https://nvd.nist.gov/vuln/detail/CVE-2026-114938
- NVD CVE-2026-115731: https://nvd.nist.gov/vuln/detail/CVE-2026-115731
- Perforce (Puppet Enterprise): https://portal.perforce.com/s/cve/a91Qi000003IaHpIAK/report-deserialization-code-execution
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- OpenSSL Security Advisory 2026-11-17: https://openssl-library.org/news/secadv/20261117.txt
- Chrome Releases (Stable Channel Update for Desktop, Nov 17): https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01699533288.html
- Chrome Releases (Extended Stable Update for Desktop, Nov 17): https://chromereleases.googleblog.com/2026/11/extended-stable-update-for-desktop_01061812727.html

FAQ

Is Java4Shell dangerous whenever Java is used?

No. Exploitation requires an x86-64 CPU with AVX-512 VBMI and crafted Base64 data reaching the vulnerable code. ARM64 is reported as not affected. However, the discoverer demonstrated unauthenticated remote code execution on major applications and a proof-of-concept is public. Rather than judging the conditions yourself, update Java.

What if we cannot update Java?

Add -XX:-UseBASE64Intrinsics to the Java startup options to stop using the vulnerable acceleration. On x86-64, -XX:UseAVX=2 also works around it, but Java fails to start on ARM. Both may affect performance, so test in a staging environment before production.

Is Java4Shell being used in real attacks?

As of Nov 18, JPCERT/CC has not confirmed exploitation in real attacks, and it is not in CISA KEV. Because a proof-of-concept is public, it is better to update before attacks begin.

Do we need to update OpenSSL right away?

As of today, the releases containing the fixes are not out (scheduled for Dec 1). OpenSSL rates all three Low, and they affect only specific usage (a QUIC server, Suite B settings, or calls that pass a non-NULL stack). After release, the regular OS or middleware update is enough.

If we do not use Puppet Enterprise, do we need to do anything?

The CVE record lists Puppet Enterprise as the affected product. If you do not use it, this item does not apply. If you use open-source Puppet, check Perforce's information to confirm how it is treated.

株式会社オブライト

Oflight Inc. is a Tokyo-based IT company providing software development, digital signage, web development, network systems, and IoT/AR/VR technology services.

Feel free to contact us

Contact Us