Cloudflare adds WAF managed rules for Java4Shell (CVE-2026-114938), OpenJDK flaw rated 9.2
The critical Base64 decoder bug affects OpenJDK 17.0.6 or newer on certain x86-64 processors; patched builds are available and Cloudflare urges updating every Java runtime.
Published 4 min read

In brief
- Java4Shell (CVE-2026-114938) is a memory-corruption flaw in OpenJDK's Base64 decoder, rated 9.2 of 10 on CVSS 4.0.
- Patched builds are out; a JVM flag is a temporary workaround.
- Cloudflare released managed WAF rules for Pro, Business and Enterprise plans, enabled by default with the Log action.
- Cloudflare says it has seen no sign of exploitation on its own infrastructure.
Cloudflare has released new WAF managed rules to help block Java4Shell (CVE-2026-114938), a memory-corruption vulnerability in the Base64 decoder of OpenJDK, the most widely used Java runtime. The security research company Calif disclosed the flaw on November 17, 2026, and it received a 9.2 of 10 (Critical) score on CVSS 4.0.
On the same day, OpenJDK published a security advisory and Oracle shipped fixed builds in its November 2026 Critical Patch Update. Cloudflare says it has seen no sign so far that Java4Shell was exploited on its own infrastructure.
What is known about the vulnerability
Base64 is a common way to represent binary data as text. On OpenJDK 17, the trigger requires 128 characters followed by =, because the threshold of the fast code path is higher there. Calif says it built its first working local exploit in about three hours with help from AI agents.
Who is affected: a specific runtime, processor and input
A system is affected only when all of these conditions hold. The Java runtime must be OpenJDK 17.0.6 or newer, including distributions built from OpenJDK such as Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK, Oracle OpenJDK, Oracle Java SE and Oracle GraalVM for JDK.
The processor must be x86-64 with AVX-512 VBMI support, such as Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, or AMD EPYC and Ryzen Zen 4 or newer. ARM64 processors are not affected. The application must also decode attacker-controlled Base64 data with the standard Java decoder.
Workarounds if you cannot patch right away
Calif documents two JVM startup flags that remove the vulnerable code path:
- -XX:-UseBASE64Intrinsics disables hardware-accelerated Base64 encoding and decoding.
- -XX:UseAVX=2 disables AVX-512. It should be applied only on x86-64 hosts, because OpenJDK on ARM does not recognize it and will fail to start.
New managed rules cover paid plans
Patching every Java runtime takes time, especially when JDKs are bundled inside applications and container images. Cloudflare's protection for paid plans is part of the Cloudflare Managed Ruleset (ID efb7b8c949ac4650a09736fc376e9aee) and covers malformed Base64 in headers, query values, body values, path segments, JWT components and WebAuthn values. The rules are available on Pro, Business and Enterprise plans and are enabled by default with the Log action.
Cloudflare is still working on a rule for the Cloudflare Free Managed Ruleset and says it will update its post when it is available.
- Encoded or nested data: the Base64 value may be wrapped inside another encoding or compressed format that the application unpacks before decoding.
- Non-HTTP protocols: some affected products, such as the Apache Kafka broker, accept traffic over their own protocols.
- Outbound connections: Calif also shared a client-side exploit, in which a Java program that opens a TLS connection to a malicious server can be compromised even if it exposes no service of its own.
- Traffic that bypasses Cloudflare, including internal traffic between services.
WAF attack score as an extra layer
The managed rule is the primary way to block malformed Base64 triggers at the edge, but WAF Attack Score, and specifically its remote code execution sub-score cf.waf.score.rce available on Enterprise plans, can add a complementary layer. As an example custom rule, Cloudflare points to blocking or challenging requests with cf.waf.score.rce le 20 on Enterprise, or cf.waf.score.class eq "attack" on Business. Cloudflare says attack score should be used alongside the explicit Base64 rules and JVM patching, since sophisticated in-memory exploits can run without sending plaintext shell commands over HTTP.
Impact on Cloudflare's own infrastructure
Cloudflare also runs Java, and checked its own systems when Java4Shell was disclosed. The company says the flaw can only be triggered on specific hardware, an x86-64 processor with AVX-512 VBMI, and that most of its Java workloads are not scheduled on vulnerable systems. About an hour after the patches were published, it began rolling out to all Java workloads a JVM startup option that disables the buggy accelerated Base64 routine, returning decoding to the standard implementation. As a precaution, it is distributing the fixed configuration to all machines regardless of hardware.
What Cloudflare recommends
Cloudflare says it expects exploit attempts to follow quickly now that the technical details are public. It recommends updating every Java runtime to patched OpenJDK builds and restarting the services that use them, or, as a temporary measure, setting -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics to eliminate the vulnerable AVX-512 code path.
Customers on paid plans who use attack score should review matches from the new managed rule and switch it to Block while patching.
- minorOfficial status now
- 187 minIncident open for
Live on Radar
Service status now: Discord, GitHub, OpenAI, Roblox and more
Follow service status live.
jkit tool
Site tool related to this subject.
Complete HTTP status code reference: meaning, causes, RFC and how to handle.
How this story was made
Drafted with the help of artificial intelligence from a fact sheet built on the sources listed below. Software checked its numbers, dates and names against that fact sheet, and Vynuo, the editor in charge, approved the text before it was published.
Sources for this story
How we know: information from an official source (Cloudflare), checked on November 19, 2026.
- OfficialHow Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938) (opens in a new tab)Cloudflare, accessed November 19, 2026
- DataStatus Cloudflare (opens in a new tab)Cloudflare Status, accessed November 19, 2026




