Sources
Read the changelog before you trust the rule
A firewall rule that moves from log to block is a vendor note. Read the note before you treat the bug as closed.
Cloudflare's web application firewall changelog dated September 30, 2026 says a detection for GitLab path traversal, CVE-2026-85706, moved from Log to Block. The same note mentions generic request-smuggling and path-traversal rules.
The changelog date is not the day the bug was disclosed. This guide is a way to read that kind of page without upgrading a log line into a fix.
Copy the change in the page's words
Write the product, the date printed on the page, and the rule name or CVE the page prints. Then write the old action and the new action. Here, the page says Log, then Block.
If the page names extra rules, list them as extra rules. Do not fold them into the CVE sentence.
Write what the page does not say
A detection moving to Block means the vendor will block requests that match that rule. It does not say every GitLab server is patched. It does not say the bug was announced on September 30.
Put that limit under the quote. A directory entry that omits the limit sends people to the wrong kind of confidence.
Point at the page, not at a retelling
Link the changelog itself. A summary on another site can drop the Log-to-Block detail or add a disclosure date the changelog does not claim.
When you review the entry later, open the same URL. If the page changed, write the new date. Do not silently replace the old note.