AI NewsInfrastructureAnnouncement
Cloudflare adds six WAF rules for Java4Shell. Patch Java anyway.
Cloudflare has released six managed WAF rules for CVE-2026-114938. The rules log matches by default. Teams still need to patch the Java runtime.

Image: Cloudflare
Why it mattersA WAF rule buys time. The fix is updating Java. Any team on OpenJDK 17.0.6 or newer on AVX-512 x86 machines has to do both.
Any team running Java on x86 servers should check the runtime version this week. Researchers at Calif disclosed Java4Shell, CVE-2026-114938, on 17 November. Cloudflare says the flaw scores 9.2 on CVSS 4.0, which puts it in the critical band. OpenJDK and Oracle released patches the same day at 21:00 UTC.
Cloudflare posted its own response on 18 November. The company released six managed WAF rules on Pro, Business and Enterprise plans. Free tier support is pending. Every rule is set to Log by default. Matches land in Security Events for review. A team switches the action to Block once it has seen the real traffic.
What the flaw does
The vulnerability is in the Base64 decoder of OpenJDK. Cloudflare calls it "a memory-corruption vulnerability" in the Base64 decoder. A remote attacker sends malformed Base64 data. The decoder overwrites memory. The attacker runs code on the server with no authentication. Two conditions must hold on the target machine. The Java runtime must be OpenJDK 17.0.6 or newer. The chip must be x86-64 with AVX-512 VBMI support. ARM64 is not affected.
What the WAF rules cover
Cloudflare matches malformed Base64 patterns in six places a request can carry data. Those are headers, query values, body values, path segments, JWT components and WebAuthn values. The post lists each rule by ID. The default Log action lets a team see real matches before blocking. The post is clear about the limits. The WAF only sees HTTP requests through Cloudflare. It cannot catch an exploit that reaches Java through a message queue or a file. It cannot catch an outbound call or any traffic that bypasses Cloudflare.
What a team should do today
Patch the Java runtime and restart the services. The post names two temporary JVM flags for a machine that cannot update at once. -XX:-UseBASE64Intrinsics turns off the vectorised Base64 code. -XX:UseAVX=2 keeps the chip below AVX-512. Both are stopgaps. The only complete fix is the vendor patch.
For Cloudflare customers, the rules are already live. Check Security Events to see whether real traffic matches. A match is a signal that production is being probed. Switching the rules from Log to Block cuts that probe at the edge. The Java runtime behind the edge then has less traffic to defend against. A team can schedule the restart on its own timeline.
Source
How Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938), Cloudflare.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.


