The rules are available for Business and Enterprise customers and are designed to catch variations and bypass attempts that signature-based rules might miss.
Key facts
| Fact | Detail | The source says |
|---|---|---|
| Vulnerability | Java4Shell (CVE-2026-114938) | “On November 17, 2026, the security research company Calif disclosed Java4Shell (CVE-2026-114938)” |
| CVSS Score | 9.2 | “Under the Common Vulnerability Scoring System (CVSS) 4.0, it scores 9.2 out of 10 (Critical)” |
| Ruleset ID | efb7b8c949ac4650a09736fc376e9aee | “Protection for paid plans has been released as part of the Cloudflare Managed Ruleset (Ruleset ID efb7b8c949ac4650a09736fc376e9aee)” |
| Default Action | Log | “The rule is enabled by default with the Log action, because blocking by default could cause false positives on legitimate Base64 traffic” |
What happened
The vulnerability was disclosed by the security research company Calif on November 17, 2026, and scored 9.2 out of 10 under the Common Vulnerability Scoring System (CVSS) 4.0. The rules are part of the Cloudflare Managed Ruleset (Ruleset ID efb7b8c949ac4650a09736fc376e9aee) and are enabled by default with the Log action to minimize false positives. Business and Enterprise customers can change the rule action to Block if legitimate traffic is not affected. The rules are designed to catch variations and bypass attempts that signature-based rules might miss.
What to weigh
- The new rules are available for Business and Enterprise customers only.
- The rules cannot block every path to the vulnerable decoder.
Source: Cloudflare

