Cloudflare WAF Adds Java4Shell Rules With Logging Enabled by Default

Cloudflare has released Java4Shell detection rules for Pro, Business and Enterprise customers, with logging enabled by default. Administrators can switch the rules to Block after confirming that…

Nov 18, 2026
•
4 min read
Technobezz
Cloudflare WAF Adds Java4Shell Rules With Logging Enabled by Default

Don't Miss the Good Stuff

Get tech news that matters delivered to your inbox.

Cloudflare has added rules to Cloudflare WAF to detect Java4Shell, a critical Java vulnerability, for customers on Pro, Business and Enterprise plans. The rules start in Log mode, so administrators must check matches and choose Block to stop matching requests. Cloudflare says it is still developing coverage for the Cloudflare Free Managed Ruleset.

The flaw, tracked as CVE-2026-114938, carries a CVSS 4.0 severity score of 9.2 out of 10 and was disclosed yesterday by Calif, a security research firm. Oracle issued patched builds at 21:00 UTC yesterday, when OpenJDK also published an advisory. Cloudflare says updating Java is the complete remedy because firewall inspection cannot reach every route through which the decoder can be attacked.

Java4Shell involves memory corruption in OpenJDK's Base64 decoder: an unauthenticated attacker can supply malformed data that overwrites adjacent memory. Calif demonstrated remote code execution before authentication against applications including Jenkins, Keycloak and Atlassian Jira in default configurations. Cloudflare says exploitation requires a separate chain for each target application and that it has found no indication of exploitation on its own infrastructure.

Exposure requires OpenJDK version 17.0.6 or later, an x86-64 processor supporting AVX-512 VBMI, and an application passing attacker-controlled Base64 into Java's standard decoder. ARM64 processors are unaffected. Applications may carry separate Java runtimes, and containers may include their own JDK, so updating the operating system's Java package does not repair those copies. Updated services also need restarting.

Cloudflare chose logging as the default because legitimate token formats can resemble malicious Base64 and automatic blocking could interrupt valid requests. Customers can inspect matches through Security Events and change the action after verifying that legitimate requests will pass. Encoded payloads, protocols outside HTTP and connections initiated by a Java application can escape WAF inspection, as can traffic routed around Cloudflare.

In October, Cloudflare extended php2shell defenses to both Free and paid WAF customers, with automatic activation for Free accounts. That deployment introduced full transaction detection, which considers server responses alongside incoming requests to help distinguish attacks from legitimate activity. For Java4Shell, Cloudflare says administrators unable to patch immediately can disable Base64 intrinsics or, on x86-64 hosts, disable AVX-512 through JVM startup flags; both measures require restarting and may affect performance.

Share