What happened

Cloudflare published new WAF rules in its Cloudflare Managed Ruleset to counter Java4Shell (CVE-2026-114938), disclosed on November 17, 2026. The rules aim to catch the malformed Base64 input patterns that trigger the flaw.

Why the flaw is critical

The bug sits in the Base64 decoder of OpenJDK, the most widely used Java runtime, and scores 9.2 out of 10 under CVSS 4.0. An unauthenticated attacker can send malformed Base64 data to overwrite memory, which can lead to heap memory leaks and remote code execution. The security research firm Calif demonstrated pre-authentication remote code execution against default configurations of Keycloak, Jira, Confluence, Jenkins and others.

Why the WAF does not block by default

The rules are enabled on Pro, Business and Enterprise plans but default to Log action, because malformed input and some benign application-specific token formats can resemble exploitation attempts. Customers can review matching requests in Security Events and switch the action to Block once they confirm legitimate traffic is unaffected.

Patching is required

Cloudflare says the WAF is an additional layer of defense, not a replacement for the patch. The flaw can be reached through paths a WAF does not see, such as outbound TLS responses. The only complete fix is updating the Java runtime; OpenJDK published an advisory and Oracle released patched builds in its November 2026 Critical Patch Update at 21:00 UTC the same day. Cloudflare says it has seen no indication of exploitation on its infrastructure so far.