A 9.2 Severity Java Flaw Has No Cloudflare WAF Rule on the Free Plan

The mitigation went out the same day as the disclosure. The plan that most people run this site on was not included in it.

Share
A 9.2 Severity Java Flaw Has No Cloudflare WAF Rule on the Free Plan

Calif disclosed Java4Shell, CVE-2026-114938, on 17 November 2026. It is a memory-corruption flaw in the Base64 decoder of OpenJDK scoring 9.2 under CVSS 4.0, allowing unauthenticated remote code execution, with demonstrated pre-auth exploits against Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. Cloudflare shipped managed WAF rules for it the same day. Those rules are available on Pro, Business and Enterprise plans. The Cloudflare Managed Ruleset they belong to is not available on the Free plan at all.1

OpenJDK published an advisory and Oracle released patched builds in its November critical patch update at 21:00 UTC on the day of disclosure. Patching is the fix. Everything else is time bought, and on a free plan the amount of time bought is zero.

Why this one is worth attention

The trigger is small enough to be alarming. Base64 padding characters in a position where valid Base64 never places them cause the intrinsic to calculate a negative output length, and that invalid length becomes a full 64-byte write past the end of the output array. A 65-character input of 64 characters followed by a single equals sign allocates a 50-byte array and then writes 62 bytes past its end.

Java does reject the input and throw an exception. By then the neighbouring memory has already been overwritten, which is why an application's own validation does not help. The corruption happens inside the decoder, before the application gets a chance to refuse the data.

The affected surface is broad and specific at the same time:2

ConditionDetail
RuntimeOpenJDK 17.0.6 or newer, including Corretto, Temurin, Zulu, Liberica, SapMachine and Oracle builds
Processorx86-64 with AVX-512 VBMI, such as Ice Lake and Sapphire Rapids Xeons, or EPYC and Zen 4
InputThe application decodes attacker-controlled Base64 with the standard Java decoder
Not affectedARM64 processors

Prices measured on 27 October 2026. Vendor plan terms, allowances and prices change without notice, so treat every figure on this page as a dated snapshot rather than a permanent fact. Where a number here differs from the vendor's own pricing page, the vendor's page is correct and the figure above is simply older than it.

Pre-authentication remote code execution was demonstrated against Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate in default configurations. Post-authentication remote code execution was demonstrated against Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. The first list is the one that matters, because it does not require a foothold first.

The plan gap, stated plainly

Cloudflare's WAF documentation lists managed ruleset availability by plan. The Free Managed Ruleset covers all four plans. The Cloudflare Managed Ruleset, which is where the Java4Shell rules were published, is available on Pro, Business and Enterprise and marked not available on Free.

RulesetFreeProBusinessEnterprise
Free Managed RulesetYesYesYesYes
Cloudflare Managed RulesetNoYesYesYes
Cloudflare OWASP Core RulesetNoYesYesYes

So the position for a free account is that the rule exists, it is maintained, it was written specifically for a 9.2 vulnerability with public proof-of-concept exploits, and it cannot be deployed. That is a different kind of gap from a metered limit, because there is no amount of careful usage that closes it.

The paid plans get more than the rules. For Business and Enterprise, WAF attack score adds a machine learning layer that rates each request for remote code execution payloads, which is what catches the variations and bypasses that signatures miss. Cloudflare also enables the new rules in Log mode by default even on the paid plans, because malformed input and some legitimate token formats look alike, and a default Block could break working applications.

What a free account can actually do

Patch. That is the real answer, and Cloudflare says as much: the WAF is an additional layer, not a replacement, and Java4Shell can arrive through paths a WAF never sees, including outbound TLS responses.

Patching is harder than it sounds here. Many applications bundle their own Java runtime and container images ship a fixed JDK, so upgrading the system Java package updates neither the bundled copies nor a JVM already running. Every updated service needs a restart, and in our experience the container images are where these upgrades stall.

If patching cannot happen immediately, Calif documents two JVM startup flags that remove the vulnerable code path. -XX:-UseBASE64Intrinsics disables hardware-accelerated Base64 entirely, and -XX:UseAVX=2 disables AVX-512. Both need a restart, both cost performance on Base64-heavy workloads, and the second one will prevent a JVM from starting on ARM. Neither replaces the update.

We read both the advisory and the WAF documentation before writing this, and the window matters: according to Cloudflare, Calif reported developing its first working local exploit in about three hours with the help of AI agents. The window between disclosure and weaponised exploits is now measured in hours, which is what makes the difference between having a WAF rule and not having one consequential.

How to read this

The verdict is that this is a serious vulnerability with a well-handled vendor response, and the free tier is excluded from the protective half of that response. The limitations for a free account are the missing managed ruleset, the absence of attack score, and a per-request body inspection limit that is 1 MB on Free, which matters because managed rules cannot fully analyse request content beyond the limit.

Our advice is to treat the JDK version you run as the control that actually matters and to stop counting the WAF as a safety net on a free plan. Best for teams already on Pro who should switch the new rules from Log to Block after reviewing matches; not ideal for anyone on Free who was assuming the managed ruleset covered them. We checked the plan matrix directly rather than inferring it from the announcement, and the row is unambiguous.

Frequently asked questions

Does the Cloudflare Free plan get Java4Shell WAF rules?
No. The rules are in the Cloudflare Managed Ruleset, which is not available on Free.

Which plans get the rules?
Pro, Business and Enterprise, enabled by default in Log mode.

Is the WAF enough on its own?
No. Cloudflare states the only complete fix is updating the Java runtime, and attacks can arrive through paths a WAF does not see.

Which Java versions are affected?
OpenJDK 17.0.6 and newer, plus distributions built from it, on x86-64 processors with AVX-512 VBMI.

Are ARM machines affected?
No. ARM64 processors are not affected.

What can I do without patching immediately?
Start the JVM with -XX:-UseBASE64Intrinsics, or -XX:UseAVX=2 on x86-64 only. Both require a restart and reduce performance.

The CVSS score, affected runtime and processor conditions, the exploitation demonstrations, the vulnerability mechanics, the mitigation flags and the patch guidance are from Cloudflare's Java4Shell analysis of 18 November 2026. The plan availability matrix, the 1 MB free request body limit and the ruleset behaviour are from Cloudflare's managed rules documentation, read on 19 November 2026. The advisory and patch release are from OpenJDK and Oracle.

Sources

  1. Cloudflare Blog: Java4Shell WAF protection: blog.cloudflare.com/java4shell-waf-protection. Used for: CVE-2026-114938, CVSS 9.2, OpenJDK 17.0.6+ on x86-64 AVX-512; pre-auth RCE against Keycloak, Jira, Confluence, Artifactory, Jenkins, PingFederate.
  2. Cloudflare Docs: Managed rules: developers.cloudflare.com/waf/managed-rules. Used for: Cloudflare Managed Ruleset is Pro and above; not available on Free; 1 MB request body limit on Free.

All sources are the vendor's own plan or documentation pages, checked on 27 October 2026. Plan terms change without notice, so confirm current limits before you rely on them.