Network Security Updates & Release Notes
38 updates curated from 1 source by the Releasebot Team. Last updated: Oct 13, 2026
- Oct 30, 2026
- Date parsed from source:Oct 30, 2026
- First seen by Releasebot:Oct 13, 2026
- Modified by Releasebot:Nov 3, 2026
Network Security by Cloudflare
Workers, BYOIP, Bots - Workers subrequests now preserve context for BYOIP destinations
Network Security from Cloudflare now preserves Workers context and original client signals for subrequests to Cloudflare-proxied BYOIP hostnames, improving security rule consistency and Bot Management accuracy while applying standard cross-zone client IP handling.
Cloudflare now preserves Workers context when a subrequest targets a Cloudflare-proxied hostname using Bring Your Own IP (BYOIP). These requests are identified as Cloudflare-to-Cloudflare traffic instead of external Internet traffic.
Previously, some BYOIP subrequests could lose Workers context and original client signals. This could cause security rules to behave unexpectedly, Bot Management to evaluate an internal Cloudflare connection instead of the original client, or affected requests to return false 403 responses.
Workers subrequests to BYOIP destinations now preserve the CF-Worker header and cf.worker.upstream_zone field. This supports consistent security rule evaluation across same-zone and cross-zone subrequests.
Bot Management fields on the destination zone now represent the original end-user connection for affected BYOIP subrequests. Bot scores, verified bot status, and JA3/JA4 fingerprints no longer represent the internal connection between Cloudflare services.
Because Cloudflare-proxied BYOIP destinations now follow standard Workers subrequest handling, cross-zone requests set CF-Connecting-IP to the Workers client IP address 2a06:98c0:3600::103 for security reasons. This applies when a Worker in one Cloudflare zone sends a subrequest to a hostname in another Cloudflare zone. Same-zone subrequests continue to reflect the client IP through CF-Connecting-IP.
For more information, refer to Cloudflare BYOIP, Workers subrequests, and CF-Connecting-IP in Worker subrequests.
Original source - Oct 15, 2026
- Date parsed from source:Oct 15, 2026
- First seen by Releasebot:Oct 16, 2026
Network Security by Cloudflare
Cloudflare WAN, Magic Transit, Cloudflare One - BGP route filtering for IPsec and GRE tunnels
Network Security adds BGP import and export filtering for Cloudflare WAN and Magic Transit tunnels, with reusable profiles that apply without resetting sessions.
Cloudflare WAN and Magic Transit IPsec and GRE tunnels now support BGP import and export filtering.
Create reusable filter profiles that specify an allow or deny action and a list of Classless Inter-Domain Routing (CIDR) targets with exact, more-specific, or prefix-length matching. Each tunnel supports one import filter and one export filter.
You can create and assign profiles through the dashboard, API, or Terraform. Profile changes apply without resetting the BGP session.
For configuration details, refer to:
- Filter BGP routes for Cloudflare WAN
- Filter BGP routes for Magic Transit
All of your release notes in one feed
Join Releasebot and get updates from Cloudflare and hundreds of other software products.
- Oct 5, 2026
- Date parsed from source:Oct 5, 2026
- First seen by Releasebot:Oct 7, 2026
Network Security by Cloudflare
Cloudflare WAN, Magic Transit, Cloudflare One - BGP over IPsec and GRE tunnels generally available
Network Security adds general availability for BGP peering over IPsec and GRE tunnels in Cloudflare WAN and Magic Transit.
BGP peering over IPsec and GRE tunnels is generally available for Cloudflare WAN and Magic Transit. You can use it for production workloads.
BGP peering exchanges routes dynamically between your devices and your Cloudflare virtual network routing table. You no longer need to update static routes manually as your network changes.
BGP over IPsec and GRE tunnels is available to all accounts that use Unified Routing. No enablement is required. BGP over CNI remains in closed beta.
For configuration details, refer to:
- Configure BGP routes for Cloudflare WAN
- Configure BGP routes for Magic Transit
- Sep 25, 2026
- Date parsed from source:Sep 25, 2026
- First seen by Releasebot:Sep 26, 2026
Network Security by Cloudflare
Cloudflare Network Firewall, Magic Transit, Cloudflare WAN - Managed Rulesets supported in Unified Routing
Network Security now supports Advanced Network Firewall Managed Rulesets for accounts using Unified Routing mode.
Cloudflare Advanced Network Firewall Managed Rulesets are now supported for accounts using Unified Routing mode.
For the full list of feature availability, refer to Check feature availability before upgrading.
Original source - Sep 18, 2026
- Date parsed from source:Sep 18, 2026
- First seen by Releasebot:Sep 19, 2026
Network Security by Cloudflare
Cloudflare WAN, Magic Transit, Cloudflare One - Unified Routing generally available
Network Security adds Unified Routing for Cloudflare WAN and Magic Transit with Automatic Return Routing and BGP support.
Unified Routing is generally available for Cloudflare WAN and Magic Transit.
Unified Routing improves the integration between Cloudflare One and the standard connectivity onramps supported by Cloudflare WAN. It is capable of many new features including Automatic Return Routing, BGP and custom client subnets.
We recommend Unified Routing for all new accounts.
For details, refer to Cloudflare WAN traffic steering and Magic Transit traffic steering.
Original source Similar to Network Security with recent updates:
- Application Security updates220 release notes · Latest Nov 12, 2026
- Cloudflare AI updates209 release notes · Latest Nov 17, 2026
- ChatGPT updates252 release notes · Latest Nov 16, 2026
- Gemini updates475 release notes · Latest Nov 18, 2026
- Claude updates194 release notes · Latest Nov 17, 2026
- macOS updates28 release notes · Latest Nov 4, 2026
- Jul 8, 2026
- Date parsed from source:Jul 8, 2026
- First seen by Releasebot:Aug 3, 2026
- Modified by Releasebot:Nov 3, 2026
Network Security by Cloudflare
Cloudflare Network Firewall, Magic Transit, Cloudflare WAN - IP lists, IDS, and SIP rules supported in Unified Routing
Network Security now supports Advanced Network Firewall IP lists, IDS, and SIP rules in Unified Routing mode for subscribed accounts.
Cloudflare Advanced Network Firewall IP lists, IDS, and SIP rules are now supported for accounts using Unified Routing mode. These features require a Cloudflare Advanced Network Firewall subscription.
Support for additional features - Threat Intel Lists, Rate Limiting, and Managed Rulesets - is planned.
For the full list of current beta limitations, refer to Traffic steering beta limitations.
Original source - May 18, 2026
- Date parsed from source:May 18, 2026
- First seen by Releasebot:May 27, 2026
Network Security by Cloudflare
Cloudflare WAN, Magic Transit - Network Analytics support for Unified Routing
Network Security adds full Network Analytics support for Unified Routing accounts, restoring traffic visibility across onramps and offramps with the same dimensions and filters as the standard data plane, with automatic collection and no configuration change required.
Network Analytics is now fully supported for accounts using Unified Routing mode. Traffic that traverses Unified Routing onramps and offramps is now visible in Network Analytics with the same dimensions and filters as traffic on the standard data plane.
This closes a parity gap for customers who had moved tunnels onto Unified Routing and lost visibility into their dataplane traffic in the Network Analytics dashboard. No configuration change is required — analytics data is collected automatically for all accounts with Unified Routing enabled.
For the remaining beta limitations, refer to Traffic steering beta limitations.
Original source - May 12, 2026
- Date parsed from source:May 12, 2026
- First seen by Releasebot:May 27, 2026
Network Security by Cloudflare
Cloudflare WAN, Magic Transit, Cloudflare One - New accounts assigned a single IPv4 anycast address
Network Security adds a default single IPv4 anycast address for Magic Transit and Cloudflare WAN accounts.
New Magic Transit and Cloudflare WAN accounts are now assigned a single IPv4 anycast address by default.
Cloudflare handles failures on its network automatically by advertising your endpoint IP from multiple nodes across many globally distributed data centers. To handle failures on your network, configure two tunnels from separate routers.
To request additional anycast IP addresses for your account, contact your account team.
For tunnel configuration guidance, refer to Configure tunnel endpoints for Cloudflare WAN or Configure tunnel endpoints for Magic Transit.
Original source - May 11, 2026
- Date parsed from source:May 11, 2026
- First seen by Releasebot:May 16, 2026
Network Security by Cloudflare
Cloudflare WAN, Magic Transit - NAT-T support for IKE on UDP port 500
Network Security adds standard NAT-T support for Cloudflare IPsec, letting devices behind NAT start IKE on UDP 500 or 4500 and complete handshakes successfully after NAT detection, with no Cloudflare config changes and no impact to existing tunnels.
Cloudflare IPsec now supports the standard NAT traversal (NAT-T) flow, where IKE begins on UDP port 500 and switches to UDP port 4500 after NAT is detected.
Previously, devices behind NAT had to be configured to initiate IKE on UDP port 4500 directly. Devices that started on UDP port 500 could not complete the IKE handshake when NAT was in the path. This required custom configuration on devices such as VeloCloud SD-WAN edges, Cisco IOS-XE routers, and Juniper SRX firewalls, and was not possible on every platform.
What changed
Devices behind NAT can now initiate IKE on either UDP port 500 or UDP port 4500.
Devices that start IKE on UDP port 500 and switch to UDP port 4500 after NAT detection now complete the handshake successfully.
No configuration change is required on Cloudflare. The change is available for all IPsec tunnels on Cloudflare WAN and Magic Transit.
This change does not affect existing tunnels:
Tunnels using UDP port 500 with no NAT detected continue to operate as before.
Tunnels configured to start IKE on UDP port 4500 continue to operate as before.
NAT detection logic is unchanged.
For configuration details, refer to GRE and IPsec tunnels.
Original source - Apr 21, 2026
- Date parsed from source:Apr 21, 2026
- First seen by Releasebot:May 7, 2026
Network Security by Cloudflare
Cloudflare Network Firewall, Magic Transit, Cloudflare WAN - Country rules supported in Unified Routing
Network Security adds Cloudflare Advanced Network Firewall Country rules for Unified Routing accounts, enabling geography-based firewall policies by source or destination country. It marks the first Advanced Network Firewall feature available in Unified Routing, with more capabilities planned.
Cloudflare Advanced Network Firewall Country rules are now supported for accounts using Unified Routing mode. This feature requires a Cloudflare Advanced Network Firewall subscription.
You can create firewall rules that match traffic based on source or destination country to enforce geographic access policies across your network.
This is the first of the Cloudflare Advanced Network Firewall features to become available in Unified Routing. Support for additional features - IP Lists, ASN Lists, Threat Intel Lists, IDS, Rate Limiting, SIP, and Managed Rulesets - is planned.
For the full list of current beta limitations, refer to Traffic steering beta limitations.
Original source - Mar 24, 2026
- Date parsed from source:Mar 24, 2026
- First seen by Releasebot:Mar 26, 2026
Network Security by Cloudflare
Network Interconnect - Interconnects moved to Connectors
Network Security removes the top-level Interconnects page and moves it to Connectors > Interconnects, with configs unchanged.
The top-level Interconnects page in the Cloudflare dashboard has been removed. Interconnects are now located under Connectors > Interconnects.
Your existing configurations and functionality remain the same.
Original source - Feb 17, 2026
- Date parsed from source:Feb 17, 2026
- First seen by Releasebot:Feb 18, 2026
Network Security by Cloudflare
Cloudflare One, Cloudflare WAN, Cloudflare Network Firewall, Network Flow - Cloudflare One Product Name Updates
Cloudflare renames networking products to align with SASE and Zero Trust, clarifying each tool’s role. Old names become Cloudflare branded equivalents, with no action needed and no changes to functionality or billing.
We are updating naming related to some of our Networking products to better clarify their place in the Zero Trust and Secure Access Service Edge (SASE) journey.
We are retiring some older brand names in favor of names that describe exactly what the products do within your network. We are doing this to help customers build better, clearer mental models for comprehensive SASE architecture delivered on Cloudflare.What's changing
- Magic WAN → Cloudflare WAN
- Magic WAN IPsec → Cloudflare IPsec
- Magic WAN GRE → Cloudflare GRE
- Magic WAN Connector → Cloudflare One Appliance
- Magic Firewall → Cloudflare Network Firewall
- Magic Network Monitoring → Network Flow
No action is required by you — all functionality, existing configurations, and billing will remain exactly the same.
For more information, visit the Cloudflare One documentation.
Original source - Jan 30, 2026
- Date parsed from source:Jan 30, 2026
- First seen by Releasebot:Jan 31, 2026
- Modified by Releasebot:Nov 3, 2026
Network Security by Cloudflare
Cloudflare WAN, Magic Transit, Cloudflare One - BGP over GRE and IPsec tunnels
Network Security now supports BGP peering for Magic WAN and Magic Transit over IPsec and GRE tunnel on-ramps in beta, helping customers automate route changes, recover sessions, secure connections with MD5 authentication, and exchange routes dynamically.
Magic WAN and Magic Transit customers can use the Cloudflare dashboard to configure and manage BGP peering between their networks and their Magic routing table when using IPsec and GRE tunnel on-ramps (beta).
Using BGP peering allows customers to:
- Automate the process of adding or removing networks and subnets.
- Take advantage of failure detection and session recovery features.
With this functionality, customers can:
- Establish an eBGP session between their devices and the Magic WAN / Magic Transit service when connected via IPsec and GRE tunnel on-ramps.
- Secure the session by MD5 authentication to prevent misconfigurations.
- Exchange routes dynamically between their devices and their Magic routing table.
For configuration details, refer to:
- Configure BGP routes for Magic WAN
- Configure BGP routes for Magic Transit
- Jan 27, 2026
- Date parsed from source:Jan 27, 2026
- First seen by Releasebot:Jan 30, 2026
Network Security by Cloudflare
Configure Cloudflare source IPs (beta)
Magic WAN now lets you set the source IP range Cloudflare uses for traffic to private networks, replacing public IPs with a dedicated private CIDR. This enables symmetric routing, better firewall state, and keeps private traffic on secure paths; IPv4 defaults to 100.64.0.0/12 (configurable to any /12), IPv6 is 2606:4700:cf1:5000::/64 (not configurable).
Magic WAN now allows you to configure the source IP address range used by Cloudflare services (such as Load Balancing, Gateway, and Browser Isolation) when sending traffic to your private networks. Previously, traffic to private networks was sourced from public Cloudflare IPs, which may have caused IP conflicts. With this feature, you can now configure a dedicated, non-Internet-routable private IP range to ensure:
- Symmetric routing over private network connections
- Proper firewall state preservation
- Private traffic stays on secure paths
Key details
- IPv4: Sourced from
100.64.0.0/12by default, configurable to any /12 CIDR - IPv6: Sourced from
2606:4700:cf1:5000::/64(not configurable) - Affected connectors: GRE, IPsec, CNI, WARP Connector, and WARP Client (Cloudflare Tunnel is not affected)
Configuring Cloudflare source IPs requires Cloudflare One Unified Routing (beta) and the "Cloudflare One Networks Write" permission.
Original source
For configuration details, refer to Configure Cloudflare source IPs. - Jan 27, 2026
- Date parsed from source:Jan 27, 2026
- First seen by Releasebot:Jan 28, 2026
- Modified by Releasebot:Jan 30, 2026
Network Security by Cloudflare
Control request and response body buffering in Configuration Rules
Cloudflare introduces configurable HTTP body buffering in Configuration Rules. Choose request buffering modes Standard, Full, or None and response buffering Standard or None, enabling or disabling inspection. Disabling buffering may affect security features like WAF and Bot Management for zones with the latest proxy.
You can now control how Cloudflare buffers HTTP request and response bodies using two new settings in Configuration Rules.
Request body buffering
Controls how Cloudflare buffers HTTP request bodies before forwarding them to your origin server:
Mode Behavior Standard (default) Cloudflare can inspect a prefix of the request body for enabled functionality such as WAF and Bot Management. Full Buffers the entire request body before sending to origin. None No buffering. The request body streams directly to origin without inspection.Response body buffering
Controls how Cloudflare buffers HTTP response bodies before forwarding them to the client:
Mode Behavior Standard (default) Cloudflare can inspect a prefix of the response body for enabled functionality. None No buffering. The response body streams directly to the client without inspection.Warning
Setting body buffering to None may break security functionality that requires body inspection, including the Web Application Firewall (WAF) and Bot Management. Ensure that any paths where you disable buffering do not require security inspection.
Availability
These settings only take effect on zones running Cloudflare's latest CDN proxy. Enterprise customers can contact their account team to enable the latest proxy on their zones.
API example
{ "action": "set_config", "action_parameters": { "request_body_buffering": "standard", "response_body_buffering": "none" } }For more information, refer to Configuration Rules.
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.