WAF virtual patch: what a rule covers and what it misses

Atlassian's advisory for CVE-2026-21589 (5 Oct 2026) names one WAF or proxy rule: block two dots next to a slash, backslash or double colon, in plain and URL-encoded form. A rule like that counts as a mitigation only in block mode, on every route to the product, until the fixed version is installed.

What this control does toward each outcome

  1. RemediateLeaves the flaw: The flaw stays in the code. Traffic the WAF does not inspect (other paths, internal callers, other protocols) and attack variants the rule does not recognize are not covered.
  2. Mitigate now, fix laterLowers exposure: Blocks or filters requests that match a known exploitation pattern before they reach the vulnerable application, without changing its code.Guidance points here
  3. Accept with a dated exceptionIf the fix date slips: accept the residual risk in a signed, dated, reviewed exception.Also allowed

Decision Table row: A control already sits in front of the vulnerable component (WAF rule, segmentation, access restriction). Group: Traffic that reaches it.

Evidence to keep: Rule ID, version and mode (block or log); Test record with date and tester; List of routes and hosts covered; Change ticket and approver; Date the rule is to be removed after the code or vendor fix.

When a WAF rule counts as a mitigation

OWASP defines a virtual patch as "A security policy enforcement layer that detects and blocks matching exploitation attempts against a known vulnerability without changing the vulnerable code." It adds the limit in the next sentence: "A virtual patch reduces exposure only for traffic the enforcement layer inspects and attack variants its rules recognize. It does not remove the underlying vulnerability." (OWASP Virtual Patching Cheat Sheet, read 19 Nov 2026.) This page covers the register entry: one rule, one product, one set of records.

Conditions drawn from the OWASP Virtual Patching Cheat Sheet, read 19 Nov 2026.
The rule counts whenThe rule does not count when
The flaw is reached by an HTTP request with a shape a filter can match, such as a path sequence or an injected string. OWASP: virtual patching "is ideally suited for injection-type flaws".The flaw is a logic or authentication error whose requests look like normal ones. OWASP says other attack types may not get "an adequate level of attack surface reduction".
Every route to the product passes through the WAF or proxy that holds the rule, including the internal hostname and any second load balancer.Some callers reach the product directly: internal clients, a second hostname, a non-HTTP protocol, or traffic the WAF does not decrypt.
The rule is in block mode and a test shows it blocks.The rule is in log-only mode, or a managed rule is disabled by default and nobody switched it on.
The rule came from the vendor's advisory or was written for the flaw class and tested against encodings.The rule matches only the one sample request from a report. OWASP says to resist this: "its long term value is significantly decreased".

The rule Atlassian named for CVE-2026-21589

CVE-2026-21589 lets an unauthenticated attacker read files under the web application root of Bitbucket, Confluence, Jira Service Management, Jira Software, Bamboo and Crowd Data Center, Crucible and Fisheye, if the attacker knows the exact file name and path. Atlassian published the advisory and fixed versions on 5 Oct 2026. CISA added the CVE to its Known Exploited Vulnerabilities catalog on 15 Oct 2026, ten days later, with a due date of 18 Oct 2026 and a forensic triage requirement (CISA KEV feed, catalog 2026.11.18, read 19 Nov 2026). Fixed builds include Confluence Data Center 9.2.26 and 10.2.19, Jira Software Data Center 9.12.40, 10.3.26 and 11.3.12, and Crucible and Fisheye 4.9.15 (Atlassian advisory, read 19 Nov 2026).

Atlassian's temporary measures, in its order: remove the instance from the internet if possible, then Option 1, a rule on the WAF or proxy layer. For Option 1 it says: "Block any URL containing this regex pattern", and "The intent of this regex is to block .. immediately adjacent to / , \ , or ::". Atlassian adds that rule implementation depends on your technology, naming a reverse proxy, AWS WAF and Cloudflare as examples, and tells you to test that the rule blocks that sequence and "handles the URL-encoded patterns". The pattern, as Atlassian printed it:

(?is).*(?:/|\\|::|%(?:25)*(?:2f|5c)|(?::|%(?:25)*3a){2})(?:\.|%(?:25)*2e){2}(?:/|\\|::|%(?:25)*(?:2f|5c)|(?::|%(?:25)*3a){2}|;|%(?:25)*3b|$).*

Option 2: Tomcat RewriteValve, for Confluence, Jira Service Management, Jira Software, Bamboo and Crowd. Atlassian's steps: back up the instance, then for each node in the Data Center cluster:

  1. Shut down the node.
  2. Find the server.xml file. On Confluence, Jira Service Management, Jira Software and Bamboo it is conf/server.xml. On Crowd it is apache-tomcat/conf/Catalina/localhost/crowd.xml or apache-tomcat/conf/server.xml, whichever holds your application's Context element. Copy the file as a backup.
  3. Find the Context element for the application (its docBase attribute is a path that includes the product name; in the standard setup it is the only Context element) and add inside it, if not already there: <Valve className="org.apache.catalina.valves.rewrite.RewriteValve" />
  4. Find the WEB-INF directory: confluence/WEB-INF on Confluence, atlassian-jira/WEB-INF on Jira Service Management and Jira Software, bamboo/WEB-INF or atlassian-bamboo/WEB-INF on Bamboo, crowd-webapp/WEB-INF on Crowd.
  5. In that directory, if rewrite.config exists, copy it as a backup and append the block below. If it does not exist, create it with the block below.
  6. Restart the node.

Primary check: Tomcat's decoded, normalized request path (no query string).

RewriteCond %{REQUEST_PATH} PATTERN
RewriteRule (?s)^.*$ /?denied [F,L]

Raw-URI fallback

RewriteCond %{REQUEST_URI} PATTERN
RewriteRule (?s)^.*$ /?denied [F,L]

In the block, PATTERN stands for the same regex printed under Option 1, character for character. Atlassian prints it on both conditions: the first checks Tomcat's decoded request path, the second the raw URI. A matching request is answered with a forbidden status.

Option 3: urlrewrite.xml, for Bitbucket Data Center only. Back up the instance. On a clustered system apply the change to all nodes, and to every Bitbucket mirror and mirror farm node. Edit <installation-directory>/app/WEB-INF/urlrewrite.xml and add a new rule element as the first rule in the file, before the other rules. The rule's from element holds the Option 1 pattern, its set element sets the status to 404, and its to element is /mvc/error404. Then restart Bitbucket Data Center. Atlassian's cost note covers both options: a legitimate URL with two dots next to a slash, backslash or double colon is denied too.

CISA's required action for the entry is to apply mitigations in accordance with vendor instructions. Atlassian's Option 1 is such an instruction, so a correctly deployed rule answers the mitigation half of the KEV entry. It does not answer the forensic triage requirement, and Atlassian says it cannot confirm whether an instance was affected and tells you to check all affected instances for signs of compromise.

What the rule costs

  • Atlassian's stated cost: any legitimate URL that contains two dots next to a slash, backslash or double colon is denied. List the product's own URLs and plugin URLs that match before the rule goes to block mode.
  • A change on the proxy or WAF layer, which usually serves other applications too. A rule written for one product but attached to a shared listener blocks those applications' requests as well.
  • Testing time. Atlassian asks for a test of plain and URL-encoded forms. OWASP warns that "A passing test for one payload does not establish complete protection".
  • Upkeep until the fix. SP 800-40 Rev. 4 says "Schedules should be set and enforced for both patch deployment and mitigation removal." (NIST SP 800-40 Rev. 4, section 3.5.3, read 19 Nov 2026.)

A dated plan for one Confluence node

Illustration: a team runs Confluence Data Center below 10.2.19 behind a reverse proxy. Rows marked plan are choices made for the example, not events. The dates marked event come from the sources above.

Example schedule. The 25 and 27 Oct dates are chosen for the illustration.
DateEvent or planRecord produced
5 Oct 2026Event: Atlassian advisory and fixed versions publishedAdvisory text quoted in the finding, with read date
15 Oct 2026Event: KEV entry added, due 18 Oct 2026. Plan: rule deployed in log-only mode on the proxy in front of ConfluenceRule ID, version, mode, change ticket
15 Oct 2026, laterPlan: review the log for hits from real users; run the owner's test requests; list URLs that matchTest record with date and tester, list of routes covered
16 Oct 2026Plan: rule moved to block mode and re-testedMode change entry, second test record
18 Oct 2026Event: KEV due date. Plan: forensic triage of the node under way, upgrade window bookedTriage ticket, upgrade ticket
25 Oct 2026Plan: Confluence upgraded to 10.2.19 and version confirmedVersion check with date
27 Oct 2026Plan: rule removed, or kept as a named hardening rule with a new ownerRemoval ticket

How to verify the rule took

  1. Read the rule back from the WAF or proxy configuration and confirm its mode is block, its pattern matches Atlassian's text character for character, and its scope names every hostname that reaches the product.
  2. Send one request of the matching shape, using only a harmless path on a system you own, and confirm the response is the block action and that the WAF log records the rule ID. Repeat once with the URL-encoded form and once with the double-encoded form, as Atlassian asks.
  3. Compare the proxy's route list with the product's real entry points, including the internal hostname, so that no path skips the rule.
  4. Re-run the check after every proxy or WAF change; add it to the change template.

Other WAF rules named in the advisories on this site

Fortinet advisory FG-IR-26-175 and Fastly blog of 16 Sep 2026, read 19 Nov 2026. The Fastly row is the WAF vendor's claim.
CVEWho named the ruleThe ruleLimit stated
CVE-2026-104286, Fortinet FortiMail (KEV 1 Oct 2026)Fortinet, advisory FG-IR-26-175If a web application firewall sits in front of FortiMail, block POST requests to /ibe that contain '../'Listed as an alternative to disabling the IBE service or limiting webmail access to trusted private networks; the upgrade is the fix
CVE-2026-75650, Adobe Commerce and Magento Open Source (KEV 8 Sep 2026)Fastly (a WAF vendor's own claim)A virtual patch for Next-Gen WAF covering each stage of the exploit chainFastly says it is defense in depth against variants and gives operators time to patch; exploitation began as early as 4 Sep 2026, three days before Adobe's bulletin on 7 Sep

What to record

WAF rule entry

  • Finding: CVE-2026-21589, Confluence Data Center, host and version
  • Source of the rule: Atlassian advisory, Option 1, read 19 Nov 2026
  • Rule ID, version, location (proxy or WAF name), attached hostnames and routes
  • Mode and the date it changed from log-only to block
  • Test record: date, tester, plain, encoded and double-encoded results
  • URLs found that match the pattern and how they were handled
  • Change ticket and approver
  • Forensic triage ticket (KEV entries marked yes)
  • Fix date and fixed version
  • Date the rule is removed or re-owned, and who confirms it

Retire or replace the rule when the fixed version is confirmed, when a test finds a path around it (OWASP: go back to analysis), or when the removal date passes with no fix. For the general decision between a rule and a fix, see the companion entries for IPS signatures and removing internet exposure.

Sources

Last reviewed