top of page
Search

Bastion Cyber Threat Brief | November 18, 2026: Java4Shell Calls for Runtime and CPU Checks

Writer: Bastion Cyber
Bastion Cyber
4 days ago
2 min read

Executive takeaway


Find the Java runtime each application actually uses before deciding its Java4Shell exposure. Prioritize public-facing services and confirm the vendor-supported update or temporary mitigation. Red Hat guidance.


What changed


On November 17, Calif disclosed Java4Shell, CVE-2026-114938, a memory-corruption flaw in OpenJDK’s Base64 decoder. Calif reports demonstrating remote code execution against applications including Jira, Jenkins, and Keycloak. It also cautions that there is no universal exploit: the application’s behavior matters. These are research demonstrations, not evidence that those deployments at your organization were attacked. Original Calif research.


Who should check


Red Hat lists its OpenJDK 17, 21, and 25 builds as affected. Exploitability requires the vulnerable decoding path, x86-64 hardware with AVX-512 VBMI support, and attacker-controlled input reaching the decoder. Red Hat says ARM64 systems and x86-64 CPUs without that support are not known to be affected. Do not apply one vendor’s version list to every Java distribution. Vendor scope and conditions.


What to do


Include runtimes bundled in applications, appliances, and containers in the inventory. Follow the product vendor’s supported update path. Red Hat recommends disabling Base64 intrinsics as an interim measure for affected JVMs while fixes are pending. Use its precise instructions, and replace temporary measures with the permanent update when available. Supported mitigation guidance.


Oracle’s November 17 releases include JDK 17.0.21.1+4 and 21.0.13.1+4. Those are Oracle build identifiers, not universal targets for other distributions. Oracle JDK 17 release notes. Oracle JDK 21 release notes.


Bastion analysis


For a growing SaaS firm or a larger enterprise in the 757, ask each application owner to document the runtime, CPU, exposure, and remediation decision together. A patch ticket for the server alone is not the evidence this review needs.


Verified as of November 18, 2026, 8:39 a.m. EST. Calif dates its disclosure November 17 and says the Oracle patch and OpenJDK advisory were released at 4 p.m. EST that day. Red Hat’s bulletin shows November 17 creation at 16:53 and update at 17:14 without a timezone; Oracle’s release notes show dates only. Disclosure and release timing.

 
 
 

Recent Posts

See All

Comments


bottom of page