Securitylab•November 21, 2026•🇷🇺Translated from Russian

Java4Shell (CVE-2026-114938) Vulnerability Allows Remote Memory Corruption and Code Execution in OpenJDK

Researchers at Calif disclosed Java4Shell (CVE-2026-114938) on 17 November 2026, a high-severity vulnerability in the Java runtime environment that allows memory corruption, theft of sensitive data and, under certain conditions, unauthenticated remote code execution. The flaw resides in the HotSpot virtual machine and affects OpenJDK along with its commercial distributions including Oracle Java, Amazon Corretto, Eclipse Temurin and Azul Zulu.

Affected Java Versions

The vulnerability was introduced in Java 17 starting with build 17.0.6 and exists in all subsequent major branches. Standard Java 8 and Java 11 builds are not affected except for Oracle’s special Enterprise Performance Pack 8u511b33-perf. The table below summarises vulnerable releases and fixes:

  • Java 8: Oracle Enterprise Performance Pack 8u511b33-perf → fixed in 8u513-perf
  • Java 11: not affected
  • Java 17: 17.0.6–17.0.21 → fixed in 17.0.21.1
  • Java 21: builds prior to 21.0.13.1
  • Java 25: builds prior to 25.0.5.1
  • Java 27: builds prior to 27.0.1.1
  • Java 18–20, 22–24, 26: all builds require migration to a supported branch

Processor Requirements

Exploitation also requires specific CPU features. The vulnerable Base64 decoder uses AVX-512 VBMI instructions present primarily in Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, as well as AMD EPYC and Ryzen processors based on Zen 4 and newer. The JVM must detect all four flags: avx512f, avx512bw, avx512vbmi and bmi2. ARM64 processors including Apple Silicon and AWS Graviton are unaffected.

Technical Details

The root cause lies in an optimised AVX-512 Base64 decoder inside HotSpot. An incorrectly handled trailing “=” character can produce a negative remaining-byte count that is misinterpreted as a bitmask, allowing a 64-byte write beyond the allocated buffer. Researchers demonstrated heap grooming techniques that corrupt adjacent object metadata, enabling arbitrary memory reads (JavaBleed) and eventual remote code execution.

Exploitable Products

Unauthenticated remote code execution was confirmed in Keycloak, Atlassian Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate. Authenticated exploitation succeeded against Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker. Custom applications built on Apache Struts and Spring Boot were also shown to be exploitable under the right conditions.

Exploits and Real-World Activity

On 17 November VulnCheck released a working remote code execution tool for its customers. The following day watchTowr observed reconnaissance requests containing “java4shell-recon” in the User-Agent header and crafted exploitation attempts. No confirmed successful compromises of production systems had been publicly reported as of 19 November 2026.

Mitigation

Administrators should immediately update to the patched versions listed above and restart all Java processes. When patching is not immediately possible, the unsafe intrinsic can be disabled with the JVM flags -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics or -XX:UseAVX=2. Web application firewalls and request filtering provide only partial protection and cannot replace a JDK update.

Related articles

Habr•Vulnerabilities & Exploits

F6 Investigates First In-the-Wild Exploitation of Critical CVE-2026-76466 in Cisco Expressway

Russian cybersecurity firm F6 has documented the first confirmed exploitation of the critical CVE-2026-76466 vulnerability (CVSS 9.8) affecting Cisco Expressway devices. Attackers targeted a Russian company and quickly adapted a public proof-of-concept exploit to gain root-level remote command execution on version X15.5.3. The flaw resides in the Erlang distribution authentication mechanism on TCP port 4372, allowing unauthenticated command execution via a hardcoded cookie. After initial access, the threat actors deployed over 100 custom Python scripts for network reconnaissance, lateral movement, and data collection, including tools that abused WinRM, SMB, LDAP, and SQL Server protocols. F6 observed modifications to the original PoC that enabled arbitrary command execution and result retrieval, along with auxiliary scripts for TCP relaying and repeated connection attempts. The incident highlights how quickly public exploits can be weaponized against perimeter devices that bridge external and internal networks.

Securitylab•Vulnerabilities & Exploits

NGINX2Root Vulnerabilities: Ten Critical Flaws Patched in NGINX Including Remote Code Execution via HTTP/2

On November 18 2026 NGINX developers addressed ten vulnerabilities with five grouped under the NGINX2Root research name by Theori's Xint team. The most severe CVE-2026-123007 enables unauthenticated remote code execution on servers with HTTP/2 enabled by exploiting memory corruption that originated in 2015. Researchers demonstrated full compromise including root escalation via a separate Linux SCTP kernel flaw and escape from Docker containers. Working exploits have been published by Rapid7 and others with specific requirements such as AVX-512 support and substantial traffic volumes. Patches are available in NGINX 1.30.7 1.31.9 and corresponding NGINX Plus releases while temporary mitigations include disabling HTTP/2 or HTTP/3. The issues affect standalone servers reverse proxies Kubernetes ingress controllers and embedded NGINX instances across distributions.

安全客•Vulnerabilities & Exploits

Linux Kernel CVE-2026-98432 Enables Remote Code Execution Across Nearly All Versions Since 4.4

China's NVDB issued a high-severity advisory on November 18 warning of a remote code execution flaw in the Linux Kernel that grants attackers full root privileges. The vulnerability affects Linux Kernel 4.4 and virtually every subsequent mainline release, impacting major distributions including Ubuntu, Debian, Red Hat, SUSE, Oracle, and Chinese variants such as Kylin, UnionTech, and Deepin. Because the flaw is remotely exploitable without prior authentication and leads directly to highest privileges, exposed public-facing systems face immediate risk. The advisory notably states that AI models can rapidly analyze patches, identify trigger conditions, and generate working exploit chains, shrinking the traditional window between disclosure and weaponization from days to hours. Official fixes have been published for multiple stable branches, yet administrators must still validate driver compatibility, container runtimes, and third-party modules before deploying kernel updates in production. The advisory also highlights incomplete vulnerability disclosures across PHP, Node.js, Apache, Chrome, GitLab, and MySQL, underscoring the need for precise asset inventories rather than reliance on vulnerability databases alone.

Habr•Vulnerabilities & Exploits

Wireshark 4.6.10 Released with Fixes for 39 Vulnerabilities and Multiple Protocol Dissectors

The open-source network protocol analyzer Wireshark has received its 4.6.10 update, addressing 14 bugs along with 39 security vulnerabilities discovered during testing. The release continues the 4.6 development branch that began in October 2025 and follows the long-standing stable line that started with version 1.0.0 in 2008. Patches cover a wide range of protocol dissectors including RTSE, NBAP, IEEE 1609.2, IrDA, Matter, IEEE 1905, OpenWire, USB-PTP, Exported PDU, ACN, PROFINET, SDP, MsgPack, NNTP, TLS, and SCTP. Additional corrections resolve infinite loops in the Kafka dissector and Tektronix K12xx file parser, heap disclosure issues, and a remote code execution flaw in LoRaWAN decryption tracked as ZDI-CAN-32851. The update also ships Npcap 1.89 for Windows installers and changes the default extcap directory on Unix-like systems to libexec for better multiarch compatibility.