How Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938)
- ID
- 47863
- Status
- summarized
- Published
- 18 Nov 2026, 10:52 PM
- Fetched
- 18 Nov 2026, 11:51 PM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/java4shell-waf-protection/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 7.5
- Created
- 18 Nov 2026, 11:51 PM
- Tags
- Audience
- developerssaas_founders
What happened
Calif disclosed Java4Shell (CVE-2026-114938), a CVSS 4.0 9.2 Critical memory-corruption bug in OpenJDK's Base64 decoder, on November 17, 2026; Oracle shipped patched builds in the November 2026 Critical Patch Update the same day at 21:00 UTC. Calif demonstrated pre-auth RCE against default-config Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins, and PingFederate, and post-auth RCE against Kafka, Solr, Elasticsearch, Gerrit, and Spinnaker. Cloudflare added Managed Ruleset signatures for Pro, Business, and Enterprise plans, but they ship in Log action by default because benign base64 token formats can resemble exploits.
Why it matters
Patch the Java runtime first: the WAF is explicitly not a substitute, and it cannot see payloads arriving via outbound TLS responses. Then check Security Events for rule matches and only switch to Block after confirming legitimate base64 traffic is unaffected — and inventory every self-hosted Keycloak, Jira, Confluence, Jenkins, Artifactory, Kafka, Solr, Elasticsearch, Gerrit, or Spinnaker instance, since those are the named default-config targets.
Discussion angle
Log-by-default is the right call for false positives, but it means nobody is actually blocked until someone reviews Security Events — who on your team owns flipping that to Block, and how do you validate against your own base64-heavy auth headers and upload paths first?