Cloudflare One Updates & Release Notes
265 updates curated from 1 source by the Releasebot Team. Last updated: Nov 18, 2026
- Nov 17, 2026
- Date parsed from source:Nov 17, 2026
- First seen by Releasebot:Nov 18, 2026
Cloudflare One Appliance, Cloudflare One, Cloudflare WAN - Configure a separate WAN gateway for each appliance in a high availability site
Cloudflare One now supports separate default gateways for each appliance in a high-availability site with a static WAN, letting appliances connect through distinct Internet circuits. Configure the secondary gateway in the dashboard or API, or leave it blank to retain the existing shared-gateway behavior.
You can now give each Cloudflare One Appliance in a high availability (HA) site its own default gateway on a static WAN. Before this change, both appliances in an HA pair shared the same WAN gateway. Now each appliance can connect to its own Internet circuit, such as a different ISP for each appliance, with its own static IP and gateway. In the dashboard, when you configure a static WAN on an HA site, enter the secondary appliance's gateway in the new Secondary gateway address field, next to Primary gateway address. In the API, set static_addressing.secondary_gateway_address when you create or update a WAN. To remove the value with a PATCH request, set it to null. The field is optional. If you leave it blank, the secondary appliance uses the primary gateway address, which matches how HA sites worked before. You can only use this field on sites in HA mode. curl --request PATCH \ https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/sites/{site_id}/wans/{wan_id} \ --header "Authorization: Bearer <API_TOKEN>" \ --header "Content-Type: application/json" \ --data '{ "static_addressing": { "address": "203.0.113.2/30", "gateway_address": "203.0.113.1", "secondary_address": "198.51.100.2/30", "secondary_gateway_address": "198.51.100.1" } }' For details, refer to About high availability configurations.
Original source - Nov 17, 2026
- Date parsed from source:Nov 17, 2026
- First seen by Releasebot:Nov 18, 2026
Risk Score - Investigate user risk events in a timeline
Cloudflare One adds a customizable risk-event timeline to User Risk Scoring, helping Enterprise teams trace triggers and later detections.
User Risk Scoring now groups risk behavior instances in a timeline. Each group highlights its trigger and shows later detections in time order. Customize the date range to focus on the events you want to investigate. Select a timeline marker to view its events. The sequence helps security teams follow how risk events relate during investigations. Switch to Table to return to the existing table view whenever you prefer. User Risk Scoring is available on Enterprise plans. For more information, refer to User risk score.
Original source All of your release notes in one feed
Join Releasebot and get updates from Cloudflare and hundreds of other software products.
- Nov 16, 2026
- Date parsed from source:Nov 16, 2026
- First seen by Releasebot:Nov 17, 2026
- Modified by Releasebot:Nov 17, 2026
Cloudflare One, Gateway - Cloudflare One adds Periodic Beaconing Traffic detection
Cloudflare One adds Periodic Beaconing Traffic as a risk behavior, identifying unusual, regular HTTP check-ins to the same destination to help teams investigate potential command-and-control activity. The feature is off by default and available on Enterprise plans.
Cloudflare One now includes Periodic Beaconing Traffic as a risk behavior. It analyzes Gateway HTTP traffic for regular check-ins to the same destination.
Cloudflare flags a user after more than 30 contacts to the same destination in six hours. Contacts must be evenly spaced, from 10 seconds to about 12 minutes apart. Few other users in your organization contact that destination.
Detection uses traffic behavior only. It does not use threat intelligence, categories, or reputation. Malware can check in with a command-and-control (
C2) server this way, but legitimate software also checks in regularly. Treat each event as a lead to investigate, not proof that a destination isC2.By default, the behavior is off and its risk level is Info. To turn it on, go to
Risk score > Risk behaviors. Cloudflare reports a continuing beacon once. Events usually arrive 3 to 6 hours after the six-hour window closes.Periodic Beaconing Traffic is available on Enterprise plans.
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
Cloudflare Tunnel, Cloudflare Tunnel for SASE - Cloudflare Tunnel extends URL normalization
Cloudflare One’s Tunnel extends URL normalization to semicolon-delimited path parameters before ingress matching, improving security for rules requiring Access validation. Normalization remains off by default for now and is scheduled to turn on in new cloudflared releases starting February 8, 2027.
Starting from version 2026.11.0, Cloudflare Tunnel extends the URL normalization introduced in 2026.10.0. Normalization now handles semicolon-delimited path parameters before matching ingress rules. This improves security for tunnels with rules that require Cloudflare Access validation. The URL path sent to your origin stays the same.
Starting 2027-02-08, new cloudflared releases will turn on URL normalization by default. This replaces the previously announced date of 2027-01-25, giving you time to test the updated behavior. Upgrade to version 2026.11.0 or later and test your path-based routing before that date, including rules that match paths containing semicolons. Configurations without rules requiring Access validation are unaffected.
This setting is currently off by default. To turn it on, run:
cloudflared tunnel --disable-path-normalization=false run <TUNNEL_NAME_OR_UUID>Alternatively, set TUNNEL_DISABLE_PATH_NORMALIZATION=false on each cloudflared replica and restart it.
For more information, refer to ingress matching and Access validation at the origin.
Original source - Nov 11, 2026
- Date parsed from source:Nov 11, 2026
- First seen by Releasebot:Nov 13, 2026
Access, Cloudflare One - GitHub automatically detects leaked Access service tokens
Cloudflare One now detects exposed Access service tokens in public GitHub repositories, disables affected tokens, and alerts administrators. The update also explains how to identify and recover leaked tokens, including required secret rotation.
GitHub secret scanning automatically detects Cloudflare Access service token secrets exposed in public repositories and reports them to Cloudflare. Access then disables the affected token and emails account administrators.
Other secret scanning tools can identify Access service tokens using their consistent Client Secret format: cfast_, followed by 40 alphanumeric characters and an eight-character hexadecimal checksum. For tools that support custom detection rules, use this regular expression to find possible secrets:
cfast_[A-Za-z0-9]{40}[a-f0-9]{8}This pattern applies to Client Secrets created on or after August 26, 2026, not legacy 64-character hexadecimal secrets. Matching the pattern does not validate the checksum or confirm that the secret is active. For details, refer to Client Secret format.
Recover a leaked service token
Before you can re-enable a leaked token, you must rotate its secret.
Leaked secrets do not support a rotation grace period. When you rotate one, the previous secret is discarded immediately. Update your services with the new secret, then re-enable the token.
For API rotations, omit previous_client_secret_expires_at. A future expiration returns 400. Attempting to re-enable the token before rotation returns 409.
For recovery steps and leak metadata fields, refer to Recover a leaked service token.
Original source Similar to Cloudflare One with recent updates:
- Cloudflare AI updates209 release notes · Latest Nov 17, 2026
- ChatGPT updates252 release notes · Latest Nov 16, 2026
- Gemini updates473 release notes · Latest Nov 17, 2026
- Claude updates194 release notes · Latest Nov 17, 2026
- Application Security updates220 release notes · Latest Nov 12, 2026
- Network Security updates38 release notes · Latest Oct 30, 2026
- Nov 10, 2026
- Date parsed from source:Nov 10, 2026
- First seen by Releasebot:Nov 11, 2026
Cloudflare One Client - Cloudflare One Client for Windows (version 2026.9.2663.1)
Cloudflare One releases a new Windows client beta with automatic Global Acceleration endpoint selection, stronger uninstall protection, and a unified diagnostics page. It also improves tunnel connectivity, network troubleshooting, performance, and reliability while fixing numerous installer, UI, and security issues.
A new Beta release for the Windows Cloudflare One Client is now available on the beta releases downloads page.
This release includes the following highlights:
- Added automatic endpoint selection for Global Acceleration. When Global Acceleration is enabled for an organization, the client connects to the Global Acceleration endpoints while the device is in the acceleration region and to the standard anycast endpoints otherwise, and reconnects when a network change moves the device between them without requiring action from the user. The Connectivity page shows which tunnel and API endpoints are in use, and users who are allowed to override the selection can choose endpoints in Settings.
- Added protection against unauthorized modification or uninstallation of the Cloudflare One Client. When enabled, the user will be asked to provide an administrator-generated code when trying to uninstall the client, which will otherwise be blocked. Users, including administrators, also can no longer stop the client service, and attempts to authorize an uninstall with a code or token, whether accepted or rejected, are reported to Cloudflare.
- Added a Diagnostics page to the client that shows the connection status and health, live tunnel and device metrics, network details and the results of DEX tests in one place. Users can run a speed test from the page that compares performance inside and outside the tunnel while the client is connected. The Troubleshooting tools button collects a full warp-diag bundle, or runs a captive portal test that briefly reconnects Wi-Fi, and saves the result to the Desktop, so users no longer need to run warp-diag from a terminal.
- The client now shows a banner when the network limits the tunnel MTU to a degraded or critically low value. The banner clears when the MTU recovers or the client disconnects.
Additional changes and improvements
- The client now applies tunnel MTUs between 1147 and 1199 bytes measured by Path MTU Discovery. Previously the client ignored these values and kept a larger MTU, which could drop larger packets on networks such as mobile hotspots while the client showed as connected.
- When Path MTU Discovery is enabled, the client now accepts larger packets from Cloudflare instead of limiting them to the size it uses for its own outbound packets.
- When Path MTU Discovery measures an IPv6 path MTU below 1280 bytes, the client now reconnects over IPv4 and keeps preferring IPv4 until the network changes. Previously the client could stay on a smaller tunnel MTU over IPv6 on networks where IPv4 supports larger packets.
- Access reauthentication requests now trust certificates in the operating system's certificate store, so reauthentication works on networks that perform TLS inspection.
- For Zero Trust deployments, the client now records a traceroute of the network path outside the tunnel when the tunnel degrades or fails to connect. warp-diag includes the same trace.
- warp-diag now includes redacted copies of the deployed MDM files and the names, but not the values, of stored registration secrets. It reports a QUIC path MTU only when one was measured.
- Added the MDM parameters mdm_file_debounce_secs (1–60) and mdm_file_unavailable_debounce_secs (0–300), which set how long the client waits before applying a changed MDM file and before acting on a missing or unreadable one.
- Added the MDM parameters managed_network_probe_interval_secs (30–300, default 30) and managed_network_probe_count (0 disables probing, 1–10, or -1 to keep probing until a managed network is found; default 1). After a registration or network change finds no managed network, the client now rechecks, so a device doesn't stay on the default profile because of a transient connection failure. Set the count to 0 to keep the previous behavior.
- Added the multicast network policy and MDM setting (allow or drop, default drop). When set to allow, the client sends traffic for multicast addresses through the tunnel instead of dropping it, for networks that use multicast ranges for other traffic.
- In proxy mode for Zero Trust, the client now sends hostnames from HTTP/HTTPS and SOCKS5 requests to Cloudflare for resolution instead of resolving them on the device.
- The Connectivity page now shows the IPv4 and IPv6 addresses assigned to the tunnel while the client is connected.
- When the app cannot reach the client service, the home screen now says why (service not running, not accepting connections, not responding, or connection dropped and reconnecting). It shows an error code and a Learn more link instead of "IPC error".
- The client now shows a notification when an administrator removes the user's selected virtual network, and shows a specific message when the user selects a virtual network that is no longer available.
- The consumer client home screen now shows when the connection is post-quantum encrypted.
- warp-cli target list now accepts --hostname to filter targets by one or more comma-separated hostnames.
- DEX HTTP tests now send a default User-Agent that identifies the Cloudflare One Client when the test does not configure one.
- Reduced CPU usage by the Windows Capability Access Manager service (camsvc) caused by the client's Wi-Fi queries.
- Reduced the client UI's memory usage.
- The client UI no longer starts WMIC or PowerShell processes to collect memory information for crash reports.
- Fixed installs failing with error 1603 on devices with Windows App Control (WDAC) policies, because some files inside the installer's custom actions were not signed. All components of the installer are now signed.
- Fixed the installer asking the user to close running applications during an upgrade, downgrade or uninstall because other programs loaded the client's Visual C++ runtime libraries through the system PATH. The client now loads these libraries from a private folder so that closing other applications is unnecessary.
- Fixed reinstalling the same version of the client from its MSI removing the updater service, which stopped the client from updating.
- Fixed the client window appearing blank or white after an upgrade, at sign-in, after waking from sleep, or after a display change.
- Fixed the client UI freezing and no longer showing status updates after the device woke from sleep.
- Fixed the client UI looking for one of its libraries in a directory that standard users can create before looking in the installation directory.
- Fixed a local user being able to crash the client service by sending a crafted query to the local DNS resolver.
- Fixed the client service restarting when a firewall update for captive portal detection stalled while the device was asleep.
- Fixed the client service leaking handles to processes after they exited, which could leave those processes listed as running.
- Fixed the client getting stuck in a disconnected state on Windows on Arm devices because leftover tunnel adapters were not removed.
- Fixed Windows resetting the Wi-Fi adapter after sign-in or a Wi-Fi restart when the client's firewall rules in Exclude split tunnel mode blocked Windows network connectivity checks. The client now allows those checks.
- Fixed the client missing some network configuration changes after the first change was detected.
- Fixed the client being unable to connect after an upgrade, downgrade, and upgrade that switched between consumer and Zero Trust registrations. The client now clears the mismatched registration so the user can register again.
- Fixed the client continuing to use the previous tunnel protocol after a key rotation for a protocol change failed. The client now retries the rotation the next time it connects.
- Fixed service token enrollment failing when it ran shortly after the service token was created. The client now retries while the new token becomes available.
- Fixed the client reconnecting repeatedly when Global Acceleration automatic endpoint selection was enabled on devices in the acceleration region, and fixed the client keeping its previous data center after the selected endpoints changed.
- Fixed a hostname-based split tunnel entry not taking effect until the next reconnect after its firewall rule failed to apply.
- Fixed the client service failing to start when a split tunnel address in mdm.xml had no prefix length. A bare IP address is now treated as a single host.
- Fixed a single malformed element in mdm.xml causing the client to ignore the whole file. warp-diag now includes the file as written.
- Fixed warp-cli dns fallback add accepting an empty domain, which sent all DNS queries to the local resolver instead of Gateway. Fallback domain and split tunnel entries are now normalized, so removing an entry matches regardless of case or a trailing dot.
- Fixed the DNS proxy caching answers for longer than the TTL of a CNAME record in the chain.
- Fixed warp-cli registration license reporting an error on slow networks even though the license was applied, which left the client registered to a WARP+ account it did not recognize.
- Fixed warp-cli debug network showing an all-zero interface GUID.
- Fixed Digital Experience Monitoring (DEX) results being reported with timestamps offset from the actual time after the system clock was corrected.
Known issues
- A Windows DNS client regression may cause connectivity check failures on systems containing large hosts files. While our client includes a mitigation for this issue, users may still experience reduced DNS performance and connectivity check failures.
- After an administrator removes a virtual network from a device profile or changes its default network, the virtual network list in the client may continue to show the previous networks until the client is restarted. This is a display issue only: the device connects to the networks its profile allows, and selecting a removed network is rejected without changing the connection. The warp-cli vnet command shows the current list. This will be addressed prior to the next GA release.
- Nov 10, 2026
- Date parsed from source:Nov 10, 2026
- First seen by Releasebot:Nov 11, 2026
Cloudflare One Client - Cloudflare One Client for macOS (version 2026.9.2663.1)
Cloudflare One releases a macOS client beta with automatic Global Acceleration endpoint selection, a unified diagnostics page, and improved network and tunnel reliability. The update also adds troubleshooting tools and clearer connection status while expanding configuration options for managed deployments.
A new Beta release for the macOS Cloudflare One Client is now available on the beta releases downloads page.
This release includes the following highlights:
- macOS 15.0 is now the minimum supported version. This release does not run on macOS 14.
- Added automatic endpoint selection for Global Acceleration. When Global Acceleration is enabled for an organization, the client connects to the Global Acceleration endpoints while the device is in the acceleration region and to the standard anycast endpoints otherwise, and reconnects when a network change moves the device between them without requiring action from the user. The Connectivity page shows which tunnel and API endpoints are in use, and users who are allowed to override the selection can choose endpoints in Settings.
- Added a Diagnostics page to the client that shows the connection status and health, live tunnel and device metrics, network details and the results of DEX tests in one place. Users can run a speed test from the page that compares performance inside and outside the tunnel while the client is connected. The Troubleshooting tools button collects a full warp-diag bundle, or runs a captive portal test that briefly reconnects Wi-Fi, and saves the result to the Desktop, so users no longer need to run warp-diag from a terminal.
- The client now shows a banner when the network limits the tunnel MTU to a degraded or critically low value. The banner clears when the MTU recovers or the client disconnects.
Additional changes and improvements
- The client now applies tunnel MTUs between 1147 and 1199 bytes measured by Path MTU Discovery. Previously the client ignored these values and kept a larger MTU, which could drop larger packets on networks such as mobile hotspots while the client showed as connected.
- When Path MTU Discovery is enabled, the client now accepts larger packets from Cloudflare instead of limiting them to the size it uses for its own outbound packets.
- When Path MTU Discovery measures an IPv6 path MTU below 1280 bytes, the client now reconnects over IPv4 and keeps preferring IPv4 until the network changes. Previously the client could stay on a smaller tunnel MTU over IPv6 on networks where IPv4 supports larger packets.
- Access reauthentication requests now trust certificates in the operating system's certificate store, so reauthentication works on networks that perform TLS inspection.
- For Zero Trust deployments, the client now records a traceroute of the network path outside the tunnel when the tunnel degrades or fails to connect. warp-diag includes the same trace.
- warp-diag now includes redacted copies of the deployed MDM files and reports a QUIC path MTU only when one was measured.
- Added the MDM parameters managed_network_probe_interval_secs (30–300, default 30) and managed_network_probe_count (0 disables probing, 1–10, or -1 to keep probing until a managed network is found; default 1). After a registration or network change finds no managed network, the client now rechecks, so a device doesn't stay on the default profile because of a transient connection failure. Set the count to 0 to keep the previous behavior.
- Added the multicast network policy and MDM setting (allow or drop, default drop). When set to allow, the client sends traffic for multicast addresses through the tunnel instead of dropping it, for networks that use multicast ranges for other traffic.
- In proxy mode for Zero Trust, the client now sends hostnames from HTTP/HTTPS and SOCKS5 requests to Cloudflare for resolution, instead of resolving them on the device.
- The Connectivity page now shows the IPv4 and IPv6 addresses assigned to the tunnel while the client is connected.
- When the app cannot reach the client service, the home screen now says why (service not running, not accepting connections, not responding, or connection dropped and reconnecting). It shows an error code and a Learn more link instead of "IPC error".
- The client now shows a notification when an administrator removes the user's selected virtual network, and shows a specific message when the user selects a virtual network that is no longer available.
- The consumer client home screen now shows when the connection is post-quantum encrypted.
- warp-cli target list now accepts --hostname to filter targets by one or more comma-separated hostnames.
- DEX HTTP tests now send a default User-Agent that identifies the Cloudflare One Client when the test does not configure one.
- The client's background services now start only when their binaries are signed by Cloudflare, so replacing the application bundle cannot run other code with the services' privileges.
- Reduced the client UI's memory usage on the home screen.
- Fixed a managed registration being removed when the MDM configuration file was briefly missing or unreadable. The client now keeps the last applied policy for 20 seconds after the file becomes unavailable. The new MDM parameters mdm_file_debounce_secs (1–60) and mdm_file_unavailable_debounce_secs (0–300) change how long the client waits before applying a changed file and before acting on a missing one.
- Fixed an upgrade sometimes leaving the client without a running service when the previous service was slow to stop. The installer now waits up to 10 seconds for the old service to be removed before starting the new one.
- Fixed the client UI not showing onboarding on first launch while a notification permission request was pending.
- Fixed the client UI crashing when the Mac woke from sleep or a display configuration changed.
- Fixed the client UI freezing and no longer showing status updates after the Mac woke from sleep.
- Fixed DNS queries failing for a short time after the Mac woke from sleep. The client now replaces stale connections to the DNS resolver during its wake connectivity check.
- Fixed the client continuing to use the previous tunnel protocol after a key rotation for a protocol change failed. The client now retries the rotation the next time it connects.
- Fixed service token enrollment failing when it ran shortly after the service token was created. The client now retries while the new token becomes available.
- Fixed the client reconnecting repeatedly when Global Acceleration automatic endpoint selection was enabled on devices in the acceleration region, and fixed the client keeping its previous data center after the selected endpoints changed.
- Fixed a hostname-based split tunnel entry not taking effect until the next reconnect after its firewall rule failed to apply.
- Fixed split tunnel updates for hostname-based entries failing when the client tried to remove a route that macOS had not installed.
- Fixed warp-cli dns fallback add accepting an empty domain, which sent all DNS queries to the local resolver instead of Gateway. Fallback domain and split tunnel entries are now normalized, so removing an entry matches regardless of case or a trailing dot.
- Fixed the DNS proxy caching answers for longer than the TTL of a CNAME record in the chain.
- Fixed warp-cli registration license reporting an error on slow networks even though the license was applied, which left the client registered to a WARP+ account it did not recognize.
- Fixed Digital Experience Monitoring (DEX) results being reported with timestamps offset from the actual time after the system clock was corrected.
- Fixed the OS version detail stored for a device keeping an outdated value, including the text "Usage: sw_vers…" reported by client versions 2023.5.587.1 through 2024.12.760.0. The client now clears the value the next time it connects.
Known issues
- After an administrator removes a virtual network from a device profile or changes its default network, the virtual network list in the client may continue to show the previous networks until the client is restarted. This is a display issue only: the device connects to the networks its profile allows, and selecting a removed network is rejected without changing the connection. The warp-cli vnet command shows the current list. This will be addressed prior to the next GA release.
- Nov 9, 2026
- Date parsed from source:Nov 9, 2026
- First seen by Releasebot:Nov 10, 2026
Email security, Cloudflare One - Improved investigation search for Email security
Cloudflare One adds a unified email security search bar with autocomplete, flexible filters, and date ranges for easier investigations.
Email security now has a unified search bar for investigations. It replaces the Email Screener side modal and makes searches easier to refine.
Search with keywords or field:value filters. Autocomplete suggests filters and values as you type. Add terms and press Enter to refine results, or select From, To, Disposition, Status, or Threat type values in results. Narrow results with a date preset or custom range.
This feature is available to all Email security customers.
Original source - Nov 6, 2026
- Date parsed from source:Nov 6, 2026
- First seen by Releasebot:Nov 7, 2026
Access, Cloudflare One - Sign in to Cloudflare Access with passkeys
Cloudflare One adds passkey sign-in for protected apps and the App Launcher, with administrator controls for enrollment and access.
Cloudflare Access supports passkeys as a login method for protected applications and the App Launcher. Users can sign in with a passkey saved on their device, security key, or password manager instead of entering a one-time PIN or configuring an identity provider.
Users verify their identity with an existing login method once before enrolling a passkey. Administrators choose which applications accept passkeys and can remove a user's registered passkeys. Access policies still determine whether a user can access an application.
For setup and enrollment instructions, refer to Passkeys.
Original source - Nov 6, 2026
- Date parsed from source:Nov 6, 2026
- First seen by Releasebot:Nov 7, 2026
Cloudflare One - Cloudflare One adds fast flux detection to UEBA
Cloudflare One adds fast flux detection as a predefined UEBA risk behavior, helping security teams identify potentially risky DNS activity and investigate it sooner. The feature is available on Enterprise plans.
Cloudflare One now includes fast flux detection as a predefined risk behavior for user and entity behavior analytics (UEBA). When enabled, detections contribute to a user's risk score.
Fast flux is a DNS technique that rapidly changes the IP addresses returned for a domain. Threat actors can use it to make malicious infrastructure harder to track and take down. Detecting it can help security teams identify potentially risky activity and investigate it sooner.
To turn on fast flux detection, go to Risk score > Risk behaviors in the Cloudflare Zero Trust dashboard.
Fast flux detection is available on Enterprise plans.
For more information, refer to User risk score.
Original source - Nov 5, 2026
- Date parsed from source:Nov 5, 2026
- First seen by Releasebot:Nov 7, 2026
Email security - Set expiration dates for Email security policies
Cloudflare One email security now supports expiration dates for allow and block policies, making temporary policy changes easier to manage.
Email security now lets you set an expiration date when creating an allow or block policy. This helps you apply temporary policy changes without removing them manually.
After the selected date passes, the policy expires and no longer applies.
This feature is available to all Email security customers, regardless of plan.
Original source - Nov 4, 2026
- Date parsed from source:Nov 4, 2026
- First seen by Releasebot:Nov 5, 2026
Browser Isolation, Cloudflare One - Block data entry with Browser Isolation without losing search, copy, and zoom (beta)
Cloudflare One adds a beta read-only keyboard option to isolation policies, blocking data entry while preserving browser actions such as search, select all, copy, print, and zoom. Copy and print continue to follow their separate policy settings.
Isolation policies now support a third keyboard option in beta: Allow read-only actions. Previously, the keyboard setting was binary — allow all input or block everything. With Allow read-only actions, you can block data entry while preserving the built-in browser actions your users depend on.
In Allow read-only actions mode, users can still find in page, select all, copy, print, and zoom. All other keyboard input is blocked from reaching the isolated page. Copy and print remain subject to their own policy settings, so the controls compose instead of overriding each other. For example, setting the keyboard to Allow read-only actions and copy to Do not allow lets users search and zoom but prevents them from copying content.
To use this feature, set Keyboard to Allow read-only actions in your isolation policy settings. Via the API, set keyboard to enable_read_only_actions in the biso_admin_controls object with version set to v2.
For more information, refer to Keyboard.
Original source - Nov 4, 2026
- Date parsed from source:Nov 4, 2026
- First seen by Releasebot:Nov 5, 2026
Cloudflare Network Firewall - New managed rule to help mitigate CVE-2026-98432.
Cloudflare One adds a managed Network Firewall rule to help mitigate Linux IPv4 TCP use-after-free vulnerability CVE-2026-98432. The rule is disabled by default and can be logged or set to block matching traffic.
Cloudflare Network Firewall has a new managed rule to help mitigate the Linux IPv4 TCP use-after-free vulnerability (CVE-2026-98432 ↗︎):
- Rule name: Block CVE-2026-98432 traffic
- Rule ID: 6a4df2bf984946a88c74b07349557e83
The rule is disabled by default. To use it:
- Go to Networking > Firewall Policies > Managed Rulesets.
- Enable the rule with action Log first.
- Review traffic that matches the rule.
- If the matching traffic is not expected for your environment, change the action to Block.
For more information on enabling managed rulesets, refer to Enable managed rulesets.
For more details about the vulnerability, including an agent assessment prompt and evidence sources, refer to the Cloudflare Radar Zero Wire briefing ↗︎.
Original source - Nov 4, 2026
- Date parsed from source:Nov 4, 2026
- First seen by Releasebot:Nov 5, 2026
Load Balancing, Cloudflare Tunnel, Cloudflare Mesh - Steer Cloudflare One users and private networks to the same endpoint with session affinity and hash steering in private load balancers
Cloudflare One now supports private load balancer session affinity, keeping users on the same healthy endpoint for stateful applications across Cloudflare Tunnel, Mesh, and WAN connections.
Private load balancers can now keep each user on the same endpoint. This helps with applications that keep session state on a single server.
Private load balancer
- Cloudflare One Client or Cloudflare WAN site
- Connects to 100.112.0.0
- Picks a healthy endpoint based on your steering policy
Health monitorsSteeringSession affinity
- Pool 1Cloudflare Tunnel
- 10.0.0.1vnet-a
- Pool 2Cloudflare Mesh node
- 10.1.0.1default
- Pool 3Cloudflare WAN
- 10.2.0.1default
Endpoint = IP address + virtual network
Two options are available:
- Hash endpoint steering. In the dashboard, set a pool's Endpoint steering to Hash. Each user is mapped to an endpoint within the pool.
- Session affinity. With the API, set session_affinity to ip_cookie on the load balancer. Each user stays on the same endpoint while it remains healthy and your pools do not change. Refer to Session affinity.
For traffic from the Cloudflare One Client, Cloudflare identifies the user by their device, so a user stays on the same endpoint even if their IP address changes. For other traffic, such as from a Cloudflare WAN site, Cloudflare uses the source IP address.
This works for endpoints reached through Cloudflare Tunnel, Cloudflare Mesh, and Cloudflare WAN. Affinity pins the endpoint, not the cloudflared or Mesh replica that carries the traffic.
To learn how private load balancing fits with your connectors, refer to Load balance private network traffic.
Original source - Nov 2, 2026
- Date parsed from source:Nov 2, 2026
- First seen by Releasebot:Nov 3, 2026
Cloudflare One, Access - Organize and authorize Access service tokens with tags
Cloudflare One now lets teams tag Access service tokens with key-value pairs, filter credentials by tag, and authorize matching tokens through Service Auth policies without listing each token individually.
You can now assign key-value tags to Access service tokens and use those tags to organize credentials or control application access. Each token supports up to five tags, such as environment: production or team: payments.
Add or edit tags when you create or update a token in the dashboard or service token API. You can search and filter by tag on the Service Tokens page. Tags also appear in Resource Tagging, where you can query them alongside other tagged resources.
The Service Token Tag policy selector matches valid tokens with an exact key-value pair. Use it in a Service Auth policy to authorize tokens by environment or team without listing each token individually. For example, this API policy configuration accepts valid tokens tagged environment: production:
{ "name": "Production service tokens", "decision": "non_identity", "include": [ { "service_token_tag": { "key": "environment", "value": "production" } } ] }For setup instructions, refer to Tag service tokens and Authorize service tokens by tag.
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official product update announcements from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.