
Cybersecurity agencies have issued urgent warnings over a newly disclosed vulnerability in Java and OpenJDK after researchers published technical details and Oracle released security fixes. The flaw, tracked as CVE-2026-114938 and widely referred to as “Java4Shell”, involves memory corruption in the Java Base64 decoding pathway and could, under specific conditions, allow an unauthenticated attacker to execute code remotely. Reuters reported that authorities in several countries urged organisations to update affected systems following the November 17 security releases.
The vulnerability does not affect every Java installation in the same way. Technical advisories say exploitation depends on particular hardware and runtime conditions, including an x86-64 processor with AVX-512 VBMI support and hardware-accelerated Base64 decoding being enabled. ARM64 systems are not known to be affected by the described issue. The European Union Agency for Cybersecurity’s CERT-EU advisory rates the flaw as high severity and recommends prioritising internet-facing applications. CERT-EU’s November 18 technical advisory explains the conditions required for exploitation and the need to update vulnerable versions.
The potential consequences are serious because Java remains widely used in enterprise applications, web services, financial platforms and government systems. A vulnerable service that accepts specially crafted input could be exposed to attempts to crash the application or, in qualifying configurations, execute unauthorised code. Red Hat’s vulnerability notice describes the issue as capable of allowing remote code execution on affected x86-64 systems, while also noting that systems without the required CPU features are not known to be vulnerable. Red Hat’s CVE record provides additional technical detail.
Oracle and the OpenJDK project released fixes on November 17, and security agencies are advising organisations to move to supported, patched versions. The NHS England cyber alert says a proof-of-concept exploit has been published and recommends applying the fixed releases. It also describes temporary mitigations for organisations that cannot patch immediately, but those measures may affect performance and should be implemented only after reviewing the official technical guidance. The NHS England advisory identifies affected platforms and links to the OpenJDK update guidance.
As of the Reuters report, authorities had not confirmed successful exploitation of the flaw in the wild. That does not remove the need for action: public proof-of-concept code can help defenders test systems, but it can also lower the barrier for attackers seeking to adapt an exploit. Organisations should inventory Java runtimes, identify internet-facing applications, check CPU capabilities and update affected deployments using official vendor packages. Security teams should also monitor logs and investigate unusual service crashes or unexpected processes. Reuters’ coverage, together with CERT-EU’s advisory, provides a useful overview of the international response.