Dashboard SCIM now supports replacing groups using HTTP PUT, as defined by RFC 7644 section 3.5.1 ↗. This allows identity providers to synchronize a group's full state, including its display name, external ID, and members, in a single request.
What's New
Group replacement via PUT: Full-state group synchronization improves compatibility with identity providers that use replacement semantics and helps keep Cloudflare groups aligned with their source identity provider.
Cloudflare Web Analytics (Real User Monitoring) is rolling out accuracy improvements to client-side soft navigations.
This change may alter the volume of pageviews reported in the dashboard and GraphQL API, though the extent depends on your front-end architecture and visitor traffic patterns.
Single Page Applications (SPAs)—such as websites built with React, Angular, Vue, or Svelte—predominantly use soft navigations. Soft navigations avoid fully unloading the current page and rendering the next one from scratch as visitors navigate.
Any client-side navigation counts as a soft navigation, including navigations intercepted by the Navigation API ↗ or triggered by the History API ↗. This means a non-SPA website can have soft navigation activity if its implementation uses these APIs.
We've extended our navigationType values to segment these different types of navigations:
navigationType
New?
Description
navigate
❌
Hard navigations that traditional websites (or "Multi Page Applications") perform when clicking links or submitting forms
soft-navigation
✅
Where the new Soft Navigation API ↗ is available and a visitor makes a client-side navigation, we record these events
routing-apis
✅
Where the native Soft Navigation API is unavailable (e.g. Safari, Firefox, older Chromium-based browsers), we fallback to measuring soft navigations using the Navigation API ↗ or History API ↗. We cannot collect LCP for these, but the other Core Web Vitals are present.
Prior to this change, we only used History API and all navigations were bucketed into navigate.
Browser Run lets you automate headless browsers on Cloudflare's global network. Run full browser sessions for interactive workflows, or use Quick Actions for one-request tasks such as screenshots, PDFs, and capturing page content.
You can now run hundreds of browser sessions in parallel, launch new browsers faster, and process three times as many Quick Actions per second. These published limits are defaults, not maximums. If your workload needs more more concurrent browsers, request higher limits ↗.
Miniflare now automatically grants local Containers the Docker privileges required for Filesystem in Userspace (FUSE). This applies to wrangler dev, the Cloudflare Vite plugin, and direct Miniflare use.
Miniflare grants these privileges when the local Docker daemon runs inside a virtual machine (VM). This includes Docker engines on macOS and through Windows Subsystem for Linux (WSL). On Linux, Miniflare grants the privileges for local rootless Docker when /dev/fuse is available.
Rootful Docker on Linux does not support FUSE by default during local development. Miniflare does not grant FUSE privileges when the Docker daemon does not meet these conditions or cannot be inspected.
Durable Object namespaces now have a Deployments tab in the Cloudflare dashboard, showing the versions of the backing Worker that are currently live and the traffic split between them.
A Durable Object namespace is backed by a Worker script, so its deployments are the same as that Worker's deployments. Previously, checking on a gradual deployment in progress for a Durable Object meant navigating to the backing Worker. The new tab surfaces that information directly on the namespace, alongside the metrics that matter for it: requests, error rate, and wall time per version.
The tab is read-only — promoting, rolling back, or splitting traffic on a deployment is still managed from the backing Worker's Deployments tab.
Actual vs. configured traffic split
The Traffic % column, for both Workers and Durable Objects, now shows the actual, observed traffic share for each version next to the percentage you configured. Previously, this column only showed the configured percentage. If you moved a deployment from 50/50 to 100% on a new version, the configured number updated immediately, but requests take time to catch up, and there was no way to tell how far along that shift was without checking metrics elsewhere.
Actual traffic share is calculated from the same GraphQL Analytics API data that powers other Workers and Durable Objects metrics, so standard ingestion delay and sampling apply. Durable Objects analytics can lag Workers analytics by several minutes, so a version's actual share may take a little longer to catch up after a change.
To view this, go to Workers & Pages > Durable Objects, select a namespace, then select the Deployments tab. For more on how gradual deployments work, refer to Gradual deployments.
OAuth client developers can now classify configured scopes as required or optional in the Cloudflare dashboard. By default, all configured scopes remain required .
What's New
Optional Scopes: OAuth clients can now mark configured scopes as optional, allowing applications to request them without requiring users to approve them.
Scope Selection: On the consent screen, users must grant required scopes but can decline optional scopes. This helps customers apply least-privilege access to applications, CLIs, and workloads. Optional scopes are selected by default.
Templates: The consent screen now includes Read Only and Full Access templates to make scope selection faster and easier.
Search: Users can now search scopes in the consent screen.
Leaked credentials detection now scans the Authorization request header for Basic Authentication credentials. Previously, the detection only inspected request bodies, query strings, and headers for well-known web applications or custom detection locations, which meant credentials sent through HTTP Basic Authentication were not covered by default.
This new default scan location decodes the Authorization: Basic <credentials> header and compares the extracted username and password against Cloudflare's database of leaked credentials, the same way as other default scan locations. Matches populate the existing leaked credentials fields, such as cf.waf.credential_check.password_leaked, and trigger the Exposed-Credential-Check managed transform header if configured, so you can reuse existing custom rules and rate limiting rules without changes.
This change was applied automatically for zones with leaked credentials detection enabled. No configuration changes are required.
This release introduces multiple features from our previous beta release into stable release, including:
When reauthentication is needed for any reason, the notifications are clearer and reduce the actions needed to get you back to work by redirecting to the browser for authentication instead of the app window when necessary.
When a network is blocking or otherwise not supportive of HTTP/3, the client will learn and adapt by switching the order of fallback for that network by starting with HTTP/2 first and then trying HTTP/3 if needed. This reduces delays in time to connectivity when joining older or heavily filtered networks.
Additional changes and improvements
Fixed a process leak in the Windows GUI that could exhaust system resources during IPC client-creation failures.
Fixed being unable to switch organizations when the client was stuck in the "Device not in organization" state.
Fixed an issue where Microsoft Defender would falsely flag the Cloudflare One Client installation as malicious when installing with Intune.
Made the Windows domain-joined posture check more reliable.
A DNS search domain parsing failure no longer prevents connection.
Cloud icon now correctly reflects actual connection status instead of showing disconnected while fully connected.
Fixed missing certificate error display due to a race condition.
Fixed empty black window after transitioning from docked dual displays to undocked/internal display.
Known issues
If a user upgrades to version 2026.7.1343.0, downgrades to an earlier version, re-registers, and then upgrades back to 2026.7.1343.0, the client might fail to connect or switch organizations. To resolve this issue, run warp-cli registration delete or warp-cli registration delete-all.
This release introduces multiple features from our previous beta release into stable release, including:
When reauthentication is needed for any reason, the notifications are clearer and reduce the actions needed to get you back to work by redirecting to the browser for authentication instead of the app window when necessary.
When a network is blocking or otherwise not supportive of HTTP/3, the client will learn and adapt by switching the order of fallback for that network by starting with HTTP/2 first and then trying HTTP/3 if needed. This reduces delays in time to connectivity when joining older or heavily filtered networks.
Additional changes and improvements
Fixed the client not allowing login to another organization when currently showing "Device not in organization."
A DNS search domain parsing failure no longer prevents connection.
Cloud icon now correctly reflects actual connection status instead of showing disconnected while fully connected.
Fixed missing certificate error display due to a race condition.
Fixed crash when trying to connect to captive portal on Wi-Fi.
Fixed empty black window after transitioning from docked dual displays to undocked/internal display.
This release introduces multiple features from our previous beta release into stable release, including:
When reauthentication is needed for any reason, the notifications are clearer and reduce the actions needed to get you back to work by redirecting to the browser for authentication instead of the app window when necessary.
When a network is blocking or otherwise not supportive of HTTP/3, the client will learn and adapt by switching the order of fallback for that network by starting with HTTP/2 first and then trying HTTP/3 if needed. This reduces delays in time to connectivity when joining older or heavily filtered networks.
Additional changes and improvements
Fixed the client not allowing login to another organization when currently showing "Device not in organization."
A DNS search domain parsing failure no longer prevents connection.
Cloud icon now correctly reflects actual connection status instead of showing disconnected while fully connected.
Fixed missing certificate error display due to a race condition.
Fixed empty black window after transitioning from docked dual displays to undocked/internal display.
Fixed hostname routes not working for Cloudflare Mesh when the IP addresses of the hostnames are local addresses.
Known issues
When in DNS Only mode, the client may send DNS queries for names that are configured for Local Domain Fallback to the encrypted DNS server instead of falling back to the system configuration. Local Domain Fallback works as expected in other client modes.
Members with only resource-scoped Access roles can now open Access resource list pages in the Cloudflare dashboard and call list endpoints in the API. They no longer need an additional account-scoped read-only role to list resources.
The dashboard and API return only resources included in the member's permission policy scopes. Filtering applies to Access applications, policies, service tokens, and identity providers. This allows administrators to delegate specific Access resources without granting account-wide visibility. Previously, the dashboard blocked these list pages and API list requests returned 403 responses.
For members with the Cloudflare Access App Admin role, policy lists include policies attached directly to the selected application. Reusable policies appear only when the member has the Cloudflare Access Policy Admin role for those policies.
GPT-5.6 Sol is available through AI Gateway, and for a limited time you can use it at 50% off. If you are already using AI Gateway, point to the openai/gpt-5.6-sol model and the discounted pricing applies automatically — no promo code needed.
The promotion is available for Unified Billing users only (not Bring Your Own Keys). Load credits onto AI Gateway and start sending requests to openai/gpt-5.6-sol.
Discounted pricing during the promotion:
Usage
Promotional price
Standard price
Input
$2.50 per 1M tokens
$5 per 1M tokens
Output
$15 per 1M tokens
$30 per 1M tokens
Cache read
$0.25 per 1M tokens
$0.50 per 1M tokens
The promotion runs through September 18, 2026. After that date, GPT-5.6 Sol requests return to standard pricing.
Version 1 of the Workers Vitest integration is published as @cloudflare/vitest-plugin ↗. The package was formerly named @cloudflare/vitest-pool-workers.
The Vitest configuration API is unchanged. Existing projects must update the dependency name, package imports, and TypeScript types entries.
You can now configure origin application settings directly in the Cloudflare dashboard when adding or editing a published application route for a Cloudflare Tunnel. These settings control how cloudflared connects to your origin server and were previously only available in the Cloudflare One dashboard or via local configuration files.
When editing a published application, expand Additional application settings to configure parameters organized into three categories:
HTTP — Set a custom HTTP Host header or disable chunked encoding.
TLS — Configure origin server name, CA pool, TLS timeout, disable TLS verification, match SNI to host, or enable HTTP/2 to origin.
Cloudflare Email Security now supports post-quantum hybrid key exchange with X25519MLKEM768 on the SMTP connections we make to receive and deliver mail. Deploying Email Security in front of a provider that supports post-quantum hybrid key agreement (like Google Workspace) will create a TLS 1.3 connection using post-quantum key agreement.
Inbound MX connections and outbound delivery connections now negotiate the X25519MLKEM768 hybrid key agreement when the peer supports it, protecting SMTP traffic against harvest-now, decrypt-later ↗ attacks.
Support is backwards compatible and enabled automatically for all customers. Senders and receivers that do not yet advertise post-quantum key agreement continue to connect with classical key exchange.
Load balancing analytics now filters traffic data by pool name instead of pool ID, aligning the query behavior with the pool names displayed in the filter dropdown.
Previously, the analytics pool filter queried by internal pool ID while displaying pool names in the UI dropdown. This mismatch caused filtering issues when pools shared similar names or when you expected results based on the visible pool name. Because the underlying query used a different identifier than what appeared on screen, the displayed data could be confusing or incorrect.
The pool filter now queries by the same pool name shown in the dropdown. When you select a pool from the filter, the analytics graphs and tables display data for that specific pool as you would expect. This change affects:
Requests over time, filtering the chart series to the selected pool.
Pool distribution, showing only the selected pool segment.
Top endpoints, displaying cards for origins in the selected pool.
Latency, showing latency data for the selected pool.
The Logs view and health event filtering are unchanged.
To use this, go to Traffic > Load Balancing Analytics for a zone. The same pool filter appears in the analytics view for an individual load balancer under Load Balancing at the account level.
R2 now supports a usjurisdiction, which guarantees that bucket data is stored and processed within the United States. Use this jurisdiction when you need explicit US data residency guarantees.
Use the jurisdiction-specific S3 endpoint to create and access buckets in the us jurisdiction:
https://<ACCOUNT_ID>.us.r2.cloudflarestorage.com
To access a bucket in the us jurisdiction from Workers, set jurisdiction in your R2 binding:
This release updates WordPress remote code execution rule metadata in the Cloudflare Managed Ruleset and Cloudflare Free Ruleset to identify CVE-2026-65640.
Key Findings
CVE-2026-65640: A remote code execution vulnerability affecting WordPress core and plugin components. Remote, unauthenticated attackers can execute arbitrary system commands to gain unauthorized access or establish backdoors on host servers.
Impact
The WordPress changes update rule metadata only; detection behavior and actions remain unchanged.
Qwen 3.8 27B is a 27-billion-parameter instruction-tuned vision language model from Alibaba's Qwen family. It processes images and text together, with reasoning and function calling for agentic workflows.
Key capabilities:
Vision: Accept image and text inputs and generate text responses.
Reasoning: Support thinking mode for complex, step-by-step problem-solving.
Function calling: Build agents that invoke tools and APIs across multiple conversation turns.
262,144 token context window: Retain long conversations and multimodal inputs across extended agent sessions.
Use Qwen 3.8 27B through the Workers AI binding (env.AI.run()) or the REST API at /ai/run. You can also use AI Gateway with these endpoints.
Cloudflare has fixed an issue affecting WebSocket data transfer reporting. HTTP Traffic Analytics and HTTP request logs now correctly count data transferred throughout a WebSocket connection, restoring the correct behavior. During the affected period, reporting captured only the initial 101 Switching Protocols handshake for some WebSocket connections, which could underreport their data transfer.
Customers with WebSocket traffic will see the correct Data Transfer in the dashboard and EdgeResponseBytes in analytics and HTTP request logs. The change reflects restored accounting of existing WebSocket traffic, not an increase in traffic caused by this change. WebSocket connection behavior is unaffected.
The separate WebSocket Analytics Logpush dataset continues to provide per-connection directional byte counts, timestamps, and close details.
For more information about HTTP Traffic Analytics, refer to Zone Analytics.
DeepSeek V4 Flash and DeepSeek V4 Pro are the first Workers AI models with a full one million (1,048,576) token context window. Use them for long-horizon agentic workflows, large codebases, and multi-step reasoning that exceed the context limits of every other model hosted on the platform.
DeepSeek V4 Flash is the faster, lower-cost sibling. This release supersedes the preview version with substantially enhanced agentic capabilities.
Key capabilities:
Reasoning: Both models support thinking mode for complex, step-by-step problem-solving.
Function calling: Build agents that invoke tools and APIs across multiple conversation turns.
Long context: Both models support a full 1,048,576 token context window.
Protect an application across all its domains at once
Until now, if a Worker was reachable on a route, a Custom Domain, and a workers.dev URL, you had to manually add each one to an Access application and keep the list in sync whenever routes or domains changed.
Now, Access attaches the policy to the Worker itself, so every associated domain and preview URL stays protected even when its routes or domains change.
Protect all new and existing Workers by default
Make all Workers private by default, so every existing and newly created Worker requires sign-in before anyone can reach it.
If a specific Worker should remain publicly accessible, add a Worker-level bypass to exempt it.
Whether you protect a single application or all Workers at once, you can choose whether to protect preview deployments only or both previews and production, and control who can sign in by Cloudflare account membership, email address, or email domain.
For more advanced policy options, edit the policy in Zero Trust ↗.
View all of your Worker Access policies
You can view and manage all of your Access policies in the Access tab of the Workers & Pages section in the dashboard.
See who is accessing your Worker
When Access is enabled on your Worker, every authenticated request includes ctx.access. Call ctx.access.getIdentity() to get the user's email, name, and groups — no manual JWT validation required.
export default { async fetch(request, env, ctx) { if (!ctx.access) { return new Response("Access did not run", { status: 401 }); } const identity = await ctx.access.getIdentity(); return Response.json({ aud: ctx.access.aud, email: identity?.email }); },};
Test Access locally
You can now test Cloudflare Access locally with wrangler dev. Add a dev block to your wrangler.jsonc:
Your Worker will receive this identity through ctx.access and ctx.access.getIdentity(), letting you test authenticated and unauthenticated flows without deploying. Remove the dev block to simulate unauthenticated requests.
API and programmatic access
You can also set up these policies through the Workers API instead of the dashboard.
Artifacts now supports jurisdictions, allowing you to select the European Union or the United States as the only location where repo data is stored and processed.
Select a jurisdiction when you create a namespace. Every repo in that namespace automatically uses the selected jurisdiction.
Cloudflare Gateway can now detect software package downloads and give you policy control over supply chain traffic. When a developer or CI/CD pipeline downloads a package through Gateway, the proxy identifies the registry protocol from the request URL and extracts the package ecosystem, name, version, and namespace. You can then write HTTP policies using pkg.* selectors to allow or block package downloads.
Supported ecosystems
Gateway detects package downloads for the following ecosystems:
Ecosystem
Namespace
npm
Scope (for example, @babel)
PyPI
--
RubyGems
--
Cargo
--
Go
Module path
Maven
Group ID
NuGet
--
Selectors
In the dashboard, select Package Ecosystem to access the package registry selectors. After selecting a single ecosystem, nested fields for package name, version, and namespace become available. Five pkg.* selectors are available for HTTP policies with the Allow and Block actions:
Selector
Description
pkg.ecosystem
The package ecosystem detected from the request URL.
pkg.name
The package name extracted from the download URL.
pkg.version
The package version, with support for ecosystem-aware comparison operators.
pkg.namespace
The package namespace, when the ecosystem supports one.
pkg.purl
The Package URL (PURL) ↗ derived from the detected coordinates. Available in the API only.
Detection is based on the registry protocol rather than the hostname, so it works the same way whether traffic goes to a public registry, a corporate proxy such as Artifactory or Nexus, or a self-hosted mirror.
Package registry security requires TLS decryption to be turned on.
