Back

Cloudflare WAF Adds Managed Rules for Java4Shell (CVE-2026-114938)
SiTech AI Team3 min read

Cloudflare WAF Adds Managed Rules for Java4Shell (CVE-2026-114938)

Cloudflare has released managed WAF rules to detect malformed Base64 patterns tied to Java4Shell, while urging teams to patch Java runtimes and restart affected services.

Cloudflare has released a new set of rules in the Cloudflare Managed Ruleset to detect malformed Base64 input patterns associated with Java4Shell (CVE-2026-114938), a critical memory-corruption vulnerability in OpenJDK's Base64 decoder disclosed on November 17, 2026. The rules are available on Pro, Business and Enterprise plans, are enabled by default with the Log action, and are meant to reduce exposure while teams patch affected Java runtimes. Cloudflare says the WAF is an additional layer of defense, not a replacement for the patch.

What Cloudflare released

The release includes rules for malformed Base64 in headers, query values, body values, path segments, Base64url JWT components and WebAuthn values. Rule IDs include 5de9b20a45ea45d3841919ab4d718bf4, 46bb4172813e471ea62d31c02337b51d, d4dc3f71f1bc44a0811ae570e5e5836c, 0dceaf0684b54fd0b085fcfb6fd6f152, 0ddd0eb664a040779f2f19065a25d991 and 4fce1ea79a614c07a27348d167d74ebb. Customers can review matching requests in Security Events and change a rule to Block once they confirm it does not affect legitimate traffic. Cloudflare is also working on a rule for the Cloudflare Free Managed Ruleset.

Who is affected and how to mitigate

Java4Shell affects a system only when OpenJDK 17.0.6 or newer runs on an x86-64 processor with AVX-512 VBMI support and the application decodes attacker-controlled Base64 with the standard Java decoder. Affected distributions include 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. ARM64 processors are not affected. If patching must wait, Calif documents two JVM startup flags: -XX:-UseBASE64Intrinsics disables hardware-accelerated Base64 encoding and decoding, while -XX:UseAVX=2 disables AVX-512 and should be applied only on x86-64 hosts. Both require a restart and may reduce performance. Many applications bundle their own Java runtime, so upgrading the system Java package does not update those copies or a running JVM; every updated service needs a restart. OpenJDK published a security advisory and Oracle released patched builds in its November 2026 Critical Patch Update on the same day, at 21:00 UTC.

WAF limits, attack score and Cloudflare's own systems

The WAF cannot block every path to the vulnerable decoder, including encoded or nested data, non-HTTP protocols such as the Apache Kafka broker, outbound TLS connections and traffic that bypasses Cloudflare. For Business and Enterprise customers, WAF attack score adds a machine learning layer that can catch multi-stage exploit chains and post-exploitation activity, although it will not flag the raw Base64 trigger in isolation. Cloudflare says its own Java workloads are largely not scheduled on vulnerable systems; about an hour after patches were published it began rolling out a JVM startup option that turns off the accelerated Base64 routine, and it is rolling the patched configuration to all machines as a precaution. Cloudflare says it has seen no indication so far that Java4Shell was exploited on Cloudflare infrastructure.

Earlier coverage: CISA მოუწოდებს Java-ს მომხმარებლებს, გამოასწორონ „Java4Shell“ ხარვეზი

Sources: Cloudflare · Cloudflare

SiTech

SiTech — AI-powered web development

We build fast, modern websites and bring AI into real business workflows. Have a project or a question? We'd love to help.