Skip to content
Cloudflare Docs

Changelog

New updates and improvements at Cloudflare.

All products
hero image
  1. You can now upload Workers with static assets (like HTML, CSS, JavaScript, images) with the Cloudflare Terraform provider v5.11.0, making it even easier to deploy and manage full-stack apps with IaC.

    Previously, you couldn't use Terraform to upload static assets without writing custom scripts to handle generating an asset manifest, calling the Cloudflare API to upload assets in chunks, and handling change detection.

    Now, you simply define the directory where your assets are built, and we handle the rest. Check out the examples for what this looks like in Terraform configuration.

    You can get started today with the Cloudflare Terraform provider (v5.11.0), using either the existing cloudflare_workers_script resource, or the beta cloudflare_worker_version resource.

    Examples

    With cloudflare_workers_script

    Here's how you can use the existing cloudflare_workers_script resource to upload your Worker code and assets in one shot.

    resource "cloudflare_workers_script" "my_app" {
    account_id = var.account_id
    script_name = "my-app"
    content_file = "./dist/worker/index.js"
    content_sha256 = filesha256("./dist/worker/index.js")
    main_module = "index.js"
    # Just point to your assets directory - that's it!
    assets = {
    directory = "./dist/static"
    }
    }

    With cloudflare_worker, cloudflare_worker_version, and cloudflare_workers_deployment

    And here's an example using the beta cloudflare_worker_version resource, alongside the cloudflare_worker and cloudflare_workers_deployment resources:

    # This tracks the existence of your Worker, so that you
    # can upload code and assets separately from tracking Worker state.
    resource "cloudflare_worker" "my_app" {
    account_id = var.account_id
    name = "my-app"
    }
    resource "cloudflare_worker_version" "my_app_version" {
    account_id = var.account_id
    worker_id = cloudflare_worker.my_app.id
    # Just point to your assets directory - that's it!
    assets = {
    directory = "./dist/static"
    }
    modules = [{
    name = "index.js"
    content_file = "./dist/worker/index.js"
    content_type = "application/javascript+module"
    }]
    }
    resource "cloudflare_workers_deployment" "my_app_deployment" {
    account_id = var.account_id
    script_name = cloudflare_worker.my_app.name
    strategy = "percentage"
    versions = [{
    version_id = cloudflare_worker_version.my_app_version.id
    percentage = 100
    }]
    }

    What's changed

    Under the hood, the Cloudflare Terraform provider now handles the same logic that Wrangler uses for static asset uploads. This includes scanning your assets directory, computing hashes for each file, generating a manifest with file metadata, and calling the Cloudflare API to upload any missing files in chunks. We support large directories with parallel uploads and chunking, and when the asset manifest hash changes, we detect what's changed and trigger an upload for only those changed files.

    Try it out

  1. You can now create and manage Workflows using Terraform, now supported in the Cloudflare Terraform provider v5.11.0. Workflows allow you to build durable, multi-step applications -- without needing to worry about retrying failed tasks or managing infrastructure.

    Now, you can deploy and manage Workflows through Terraform using the new cloudflare_workflow resource:

    resource "cloudflare_workflow" "my_workflow" {
    account_id = var.account_id
    workflow_name = "my-workflow"
    class_name = "MyWorkflow"
    script_name = "my-worker"
    }

    Examples

    Here are full examples of how to configure cloudflare_workflow in Terraform, using the existing cloudflare_workers_script resource, and the beta cloudflare_worker_version resource.

    With cloudflare_workflow and cloudflare_workers_script

    resource "cloudflare_workers_script" "workflow_worker" {
    account_id = var.cloudflare_account_id
    script_name = "my-workflow-worker"
    content_file = "${path.module}/../dist/worker/index.js"
    content_sha256 = filesha256("${path.module}/../dist/worker/index.js")
    main_module = "index.js"
    }
    resource "cloudflare_workflow" "workflow" {
    account_id = var.cloudflare_account_id
    workflow_name = "my-workflow"
    class_name = "MyWorkflow"
    script_name = cloudflare_workers_script.workflow_worker.script_name
    }

    With cloudflare_workflow, and the new beta resources

    You can more granularly control the lifecycle of each Worker resource using the beta cloudflare_worker_version resource, alongside the cloudflare_worker and cloudflare_workers_deployment resources.

    resource "cloudflare_worker" "workflow_worker" {
    account_id = var.cloudflare_account_id
    name = "my-workflow-worker"
    }
    resource "cloudflare_worker_version" "workflow_worker_version" {
    account_id = var.cloudflare_account_id
    worker_id = cloudflare_worker.workflow_worker.id
    main_module = "index.js"
    modules = [{
    name = "index.js"
    content_file = "${path.module}/../dist/worker/index.js"
    content_type = "application/javascript+module"
    }]
    }
    resource "cloudflare_workers_deployment" "workflow_deployment" {
    account_id = var.cloudflare_account_id
    script_name = cloudflare_worker.workflow_worker.name
    strategy = "percentage"
    versions = [{
    version_id = cloudflare_worker_version.workflow_worker_version.id
    percentage = 100
    }]
    }
    resource "cloudflare_workflow" "my_workflow" {
    account_id = var.cloudflare_account_id
    workflow_name = "my-workflow"
    class_name = "MyWorkflow"
    script_name = cloudflare_worker.workflow_worker.name
    }

    Try it out

  1. A new GA release for the Linux WARP client is now available on the stable releases downloads page.

    This release contains significant fixes and improvements including an updated public key for Linux packages. The public key must be updated if it was installed before September 12, 2025 to ensure the repository remains functional after December 4, 2025. Instructions to make this update are available at pkg.cloudflareclient.com.

    Changes and improvements

    • Proxy mode has been enhanced for even faster resolution. Proxy mode now supports SOCKS4, SOCK5, and HTTP CONNECT over an L4 tunnel with custom congestion control optimizations instead of the previous L3 tunnel to Cloudflare's network. This has more than doubled Proxy mode throughput in lab speed testing, by an order of magnitude in some cases.

    • The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new WARP mode or switch to the MASQUE protocol. Otherwise, all devices matching the profile will lose connectivity.

    Known issues

    • Devices using WARP client 2025.4.929.0 and up may experience Local Domain Fallback failures if a fallback server has not been configured. To configure a fallback server, refer to Route traffic to fallback server.
  1. A new GA release for the Windows WARP client is now available on the stable releases downloads page.

    This release contains significant fixes and improvements.

    Changes and improvements

    • Proxy mode has been enhanced for even faster resolution. Proxy mode now supports SOCKS4, SOCK5, and HTTP CONNECT over an L4 tunnel with custom congestion control optimizations instead of the previous L3 tunnel to Cloudflare's network. This has more than doubled Proxy mode throughput in lab speed testing, by an order of magnitude in some cases.

    • The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new WARP mode or switch to the MASQUE protocol. Otherwise, all devices matching the profile will lose connectivity.

    Known issues

    • For Windows 11 24H2 users, Microsoft has confirmed a regression that may lead to performance issues like mouse lag, audio cracking, or other slowdowns. Cloudflare recommends users experiencing these issues upgrade to a minimum Windows 11 24H2 KB5062553 or higher for resolution.

    • Devices using WARP client 2025.4.929.0 and up may experience Local Domain Fallback failures if a fallback server has not been configured. To configure a fallback server, refer to Route traffic to fallback server.

    • Devices with KB5055523 installed may receive a warning about Win32/ClickFix.ABA being present in the installer. To resolve this false positive, update Microsoft Security Intelligence to version 1.429.19.0 or later.

    • DNS resolution may be broken when the following conditions are all true:

      • WARP is in Secure Web Gateway without DNS filtering (tunnel-only) mode.
      • A custom DNS server address is configured on the primary network adapter.
      • The custom DNS server address on the primary network adapter is changed while WARP is connected.

      To work around this issue, reconnect the WARP client by toggling off and back on.

  1. A new GA release for the macOS WARP client is now available on the stable releases downloads page.

    This release contains significant fixes and improvements.

    Changes and improvements

    • Proxy mode has been enhanced for even faster resolution. Proxy mode now supports SOCKS4, SOCK5, and HTTP CONNECT over an L4 tunnel with custom congestion control optimizations instead of the previous L3 tunnel to Cloudflare's network. This has more than doubled Proxy mode throughput in lab speed testing, by an order of magnitude in some cases.

    • The MASQUE protocol is now the only protocol that can use Proxy mode. If you previously configured a device profile to use Proxy mode with Wireguard, you will need to select a new WARP mode or switch to the MASQUE protocol. Otherwise, all devices matching the profile will lose connectivity.

    Known issues

    • macOS Sequoia: Due to changes Apple introduced in macOS 15.0.x, the WARP client may not behave as expected. Cloudflare recommends the use of macOS 15.4 or later.

    • Devices using WARP client 2025.4.929.0 and up may experience Local Domain Fallback failures if a fallback server has not been configured. To configure a fallback server, refer to Route traffic to fallback server.

  1. The most common reason users contact Cloudflare support is lost two-factor authentication (2FA) credentials. Cloudflare supports both app-based and hardware keys for 2FA, but you could lose access to your account if you lose these. Over the past few weeks, we have been rolling out email and in-product reminders that remind you to also download backup codes (sometimes called recovery keys) that can get you back into your account in the event you lose your 2FA credentials. Download your backup codes now by logging into Cloudflare, then navigating to Profile > Security & Authentication > Backup codes.

    Sign-in security best practices

    Cloudflare is critical infrastructure, and you should protect it as such. Please review the following best practices and make sure you are doing your part to secure your account.

    • Use a unique password for every website, including Cloudflare, and store it in a password manager like 1Password or Keeper. These services are cross-platform and simplify the process of managing secure passwords.
    • Use 2FA to make it harder for an attacker to get into your account in the event your password is leaked
    • Store your backup codes securely. A password manager is the best place since it keeps the backup codes encrypted, but you can also print them and put them somewhere safe in your home.
    • If you use an app to manage your 2FA keys, enable cloud backup, so that you don't lose your keys in the event you lose your phone.
    • If you use a custom email domain to sign in, configure SSO.
    • If you use a public email domain like Gmail or Hotmail, you can also use social login with Apple, GitHub, or Google to sign in.
    • If you manage a Cloudflare account for work:
      • Have at least two administrators in case one of them unexpectedly leaves your company
      • Use SCIM to automate permissions management for members in your Cloudflare account
  1. This week highlights multiple critical Cisco vulnerabilities (CVE-2025-20363, CVE-2025-20333, CVE-2025-20362). This flaw stems from improper input validation in HTTP(S) requests. An authenticated VPN user could send crafted requests to execute code as root, potentially compromising the device. The initial two rules were made available on September 28, with a third rule added today, October 7, for more robust protection.

    • Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Multiple vulnerabilities that could allow attackers to exploit unsafe deserialization and input validation flaws. Successful exploitation may result in arbitrary code execution, privilege escalation, or command injection on affected systems.

    Impact

    Cisco (CVE-2025-20333, CVE-2025-20362, CVE-2025-20363): Exploitation enables attackers to escalate privileges or achieve remote code execution via command injection. Administrators are strongly advised to apply vendor updates immediately.

    RulesetRule IDLegacy Rule IDDescriptionPrevious ActionNew ActionComments
    Cloudflare Managed Ruleset 100788BCisco Secure Firewall Adaptive Security Appliance - Remote Code Execution - CVE:CVE-2025-20333, CVE:CVE-2025-20362, CVE:CVE-2025-20363N/ABlockThis is a New Detection
  1. Screenshot of the Workers overview page in the Cloudflare dashboard

    Each of your Workers now has a new overview page in the Cloudflare dashboard.

    The goal is to make it easier to understand your Worker without digging through multiple tabs. Think of it as a new home base, a place to get a high-level overview on what's going on.

    It's the first place you land when you open a Worker in the dashboard, and it gives you an immediate view of what’s going on. You can see requests, errors, and CPU time at a glance. You can view and add bindings, and see recent versions of your app, including who published them.

    Navigation is also simpler, with visually distinct tabs at the top of the page. At the bottom right you'll find guided steps for what to do next that are based on the state of your Worker, such as adding a binding or connecting a custom domain.

    We plan to add more here over time. Better insights, more controls, and ways to manage your Worker from one page.

    If you have feedback or suggestions for the new Overview page or your Cloudflare Workers experience in general, we'd love to hear from you. Join the Cloudflare developer community on Discord.

  1. You can now enable compaction for individual Apache Iceberg tables in R2 Data Catalog, giving you fine-grained control over different workloads.

    Terminal window
    # Enable compaction for a specific table (no token required)
    npx wrangler r2 bucket catalog compaction enable <BUCKET> <NAMESPACE> <TABLE> --target-size 256

    This allows you to:

    • Apply different target file sizes per table
    • Disable compaction for specific tables
    • Optimize based on table-specific access patterns

    Learn more at Manage catalogs.

  1. Radar now includes browser detection for Post-quantum (PQ) encryption. The Post-quantum encryption card now checks whether a user’s browser supports post-quantum encryption. If support is detected, information about the key agreement in use is displayed.

    Screenshot of the PQ encryption browser support test on the Adoption & Usage page
  1. This week’s highlights prioritise an emergency Oracle E-Business Suite RCE rule deployed to block active, high-impact exploitation. Also addressed are high-severity Chaos Mesh controller command-injection flaws that enable unauthenticated in-cluster RCE and potential cluster compromise, plus a form-data multipart boundary issue that permits HTTP Parameter Pollution (HPP). Two new generic SQLi detections were added to catch inline-comment obfuscation and information disclosure techniques.

    Key Findings

    • New emergency rule released for Oracle E-Business Suite (CVE-2025-61882) addressing an actively exploited remote code execution vulnerability in core business application modules. Immediate mitigation deployed to protect enterprise workloads.

    • Chaos Mesh (CVE-2025-59358,CVE-2025-59359,CVE-2025-59360,CVE-2025-59361): A GraphQL debug endpoint on the Chaos Controller Manager is exposed without authentication; several controller mutations (cleanTcs, killProcesses, cleanIptables) are vulnerable to OS command injection.

    • Form-Data (CVE-2025-7783): Attackers who can observe Math.random() outputs and control request fields in form-data may exploit this flaw to perform HTTP parameter pollution, leading to request tampering or data manipulation.

    • Two new generic SQLi detections added to enhance baseline coverage against inline-comment obfuscation and information disclosure attempts.

    Impact

    • CVE-2025-61882 — Oracle E-Business Suite remote code execution (emergency detection): attacker-controlled input can yield full system compromise, data exfiltration, and operational outage; immediate blocking enforced.

    • CVE-2025-59358 / CVE-2025-59359 / CVE-2025-59360 / CVE-2025-59361 — Unauthenticated command-injection in Chaos Mesh controllers allowing remote code execution, cluster compromise, and service disruption (high availability risk).

    • CVE-2025-7783 — Predictable multipart boundaries in form-data enabling HTTP Parameter Pollution; results include request tampering, parameter overwrite, and downstream data integrity loss.

    RulesetRule IDLegacy Rule IDDescriptionPrevious ActionNew ActionComments
    Cloudflare Managed Ruleset 100882Chaos Mesh - Missing Authentication - CVE:CVE-2025-59358LogDisabledThis is a New Detection
    Cloudflare Managed Ruleset 100883Chaos Mesh - Command Injection - CVE:CVE-2025-59359LogBlockThis is a New Detection
    Cloudflare Managed Ruleset 100884Chaos Mesh - Command Injection - CVE:CVE-2025-59361LogBlockThis is a New Detection
    Cloudflare Managed Ruleset 100886Form-Data - Parameter Pollution - CVE:CVE-2025-7783LogBlockThis is a New Detection
    Cloudflare Managed Ruleset 100888Chaos Mesh - Command Injection - CVE:CVE-2025-59360LogBlockThis is a New Detection
    Cloudflare Managed Ruleset 100916Oracle E-Business Suite - Remote Code Execution - CVE:CVE-2025-61882N/ABlockThis is a New Detection
    Cloudflare Managed Ruleset 100917Generic Rules - SQLi - Inline Comment InjectionN/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100918Generic Rules - SQLi - Information DisclosureN/ADisabledThis is a New Detection
  1. Managed Ruleset Updated

    This update introduces 21 new detections in the Cloudflare Managed Ruleset (all currently set to Disabled mode to preserve remediation logic and allow quick activation if needed). The rules cover a broad spectrum of threats - SQL injection techniques, command and code injection, information disclosure of common files, URL anomalies, and cross-site scripting.

    RulesetRule IDLegacy Rule IDDescriptionPrevious ActionNew ActionComments
    Cloudflare Managed Ruleset 100902Generic Rules - Command Execution - 2N/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100908Generic Rules - Command Execution - 3N/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100910Generic Rules - Command Execution - 4N/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100915Generic Rules - Command Execution - 5N/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100899Generic Rules - Content-Type AbuseN/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100914Generic Rules - Content-Type InjectionN/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100911Generic Rules - Cookie Header InjectionN/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100905Generic Rules - NoSQL InjectionN/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100913Generic Rules - NoSQL Injection - 2N/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100907Generic Rules - Parameter PollutionN/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100906Generic Rules - PHP Object InjectionN/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100904Generic Rules - Prototype PollutionN/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100897Generic Rules - Prototype Pollution 2N/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100903Generic Rules - Reverse ShellN/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100909Generic Rules - Reverse Shell - 2N/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100898Generic Rules - SSJI NoSQLN/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100896Generic Rules - SSRFN/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100895Generic Rules - Template InjectionN/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100895AGeneric Rules - Template Injection - 2N/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100912Generic Rules - XXEN/ADisabledThis is a New Detection
    Cloudflare Managed Ruleset 100900Relative Paths - Anomaly HeadersN/ADisabledThis is a New Detection
  1. You can now enable Cloudflare Access for your workers.dev and Preview URLs in a single click.

    Screenshot of the Enable/Disable Cloudflare Access button on the workers.dev route settings page

    Access allows you to limit access to your Workers to specific users or groups. You can limit access to yourself, your teammates, your organization, or anyone else you specify in your Access policy.

    To enable Cloudflare Access:

    1. In the Cloudflare dashboard, go to the Workers & Pages page.

      Go to Workers & Pages
    2. In Overview, select your Worker.

    3. Go to Settings > Domains & Routes.

    4. For workers.dev or Preview URLs, click Enable Cloudflare Access.

    5. Optionally, to configure the Access application, click Manage Cloudflare Access. There, you can change the email addresses you want to authorize. View Access policies to learn about configuring alternate rules.

    To fully secure your application, it is important that you validate the JWT that Cloudflare Access adds to the Cf-Access-Jwt-Assertion header on the incoming request.

    The following code will validate the JWT using the jose NPM package:

    JavaScript
    import { jwtVerify, createRemoteJWKSet } from "jose";
    export default {
    async fetch(request, env, ctx) {
    // Verify the POLICY_AUD environment variable is set
    if (!env.POLICY_AUD) {
    return new Response("Missing required audience", {
    status: 403,
    headers: { "Content-Type": "text/plain" },
    });
    }
    // Get the JWT from the request headers
    const token = request.headers.get("cf-access-jwt-assertion");
    // Check if token exists
    if (!token) {
    return new Response("Missing required CF Access JWT", {
    status: 403,
    headers: { "Content-Type": "text/plain" },
    });
    }
    try {
    // Create JWKS from your team domain
    const JWKS = createRemoteJWKSet(
    new URL(`${env.TEAM_DOMAIN}/cdn-cgi/access/certs`),
    );
    // Verify the JWT
    const { payload } = await jwtVerify(token, JWKS, {
    issuer: env.TEAM_DOMAIN,
    audience: env.POLICY_AUD,
    });
    // Token is valid, proceed with your application logic
    return new Response(`Hello ${payload.email || "authenticated user"}!`, {
    headers: { "Content-Type": "text/plain" },
    });
    } catch (error) {
    // Token verification failed
    return new Response(`Invalid token: ${error.message}`, {
    status: 403,
    headers: { "Content-Type": "text/plain" },
    });
    }
    },
    };

    Required environment variables

    Add these environment variables to your Worker:

    • POLICY_AUD: Your application's AUD tag
    • TEAM_DOMAIN: https://<your-team-name>.cloudflareaccess.com

    Both of these appear in the modal that appears when you enable Cloudflare Access.

    You can set these variables by adding them to your Worker's Wrangler configuration file, or via the Cloudflare dashboard under Workers & Pages > your-worker > Settings > Environment Variables.

  1. Fine-grained permissions for Access Applications, Identity Providers (IdPs), and Targets is now available in Public Beta. This expands our RBAC model beyond account & zone-scoped roles, enabling administrators to grant permissions scoped to individual resources.

    What's New

    Updated Permissions Policy UX

    For more info:

  1. Deepgram's newest Flux model @cf/deepgram/flux is now available on Workers AI, hosted directly on Cloudflare's infrastructure. We're excited to be a launch partner with Deepgram and offer their new Speech Recognition model built specifically for enabling voice agents. Check out Deepgram's blog for more details on the release.

    The Flux model can be used in conjunction with Deepgram's speech-to-text model @cf/deepgram/nova-3 and text-to-speech model @cf/deepgram/aura-1 to build end-to-end voice agents. Having Deepgram on Workers AI takes advantage of our edge GPU infrastructure, for ultra low latency voice AI applications.

    Promotional Pricing

    For the month of October 2025, Deepgram's Flux model will be free to use on Workers AI. Official pricing will be announced soon and charged after the promotional pricing period ends on October 31, 2025. Check out the model page for pricing details in the future.

    Example Usage

    The new Flux model is WebSocket only as it requires live bi-directional streaming in order to recognize speech activity.

    1. Create a worker that establishes a websocket connection with @cf/deepgram/flux
    JavaScript
    export default {
    async fetch(request, env, ctx): Promise<Response> {
    const resp = await env.AI.run("@cf/deepgram/flux", {
    encoding: "linear16",
    sample_rate: "16000"
    }, {
    websocket: true
    });
    return resp;
    },
    } satisfies ExportedHandler<Env>;
    1. Deploy your worker
    Terminal window
    npx wrangler deploy
    1. Write a client script to connect to your worker and start sending random audio bytes to it
    JavaScript
    const ws = new WebSocket('wss://<your-worker-url.com>');
    ws.onopen = () => {
    console.log('Connected to WebSocket');
    // Generate and send random audio bytes
    // You can replace this part with a function
    // that reads from your mic or other audio source
    const audioData = generateRandomAudio();
    ws.send(audioData);
    console.log('Audio data sent');
    };
    ws.onmessage = (event) => {
    // Transcription will be received here
    // Add your custom logic to parse the data
    console.log('Received:', event.data);
    };
    ws.onerror = (error) => {
    console.error('WebSocket error:', error);
    };
    ws.onclose = () => {
    console.log('WebSocket closed');
    };
    // Generate random audio data (1 second of noise at 44.1kHz, mono)
    function generateRandomAudio() {
    const sampleRate = 44100;
    const duration = 1;
    const numSamples = sampleRate * duration;
    const buffer = new ArrayBuffer(numSamples * 2);
    const view = new Int16Array(buffer);
    for (let i = 0; i < numSamples; i++) {
    view[i] = Math.floor(Math.random() * 65536 - 32768);
    }
    return buffer;
    }
  1. You can now perform more powerful queries directly in Workers Analytics Engine with a major expansion of our SQL function library.

    Workers Analytics Engine allows you to ingest and store high-cardinality data at scale (such as custom analytics) and query your data through a simple SQL API.

    Today, we've expanded Workers Analytics Engine's SQL capabilities with several new functions:

    New aggregate functions:

    • argMin() - Returns the value associated with the minimum in a group
    • argMax() - Returns the value associated with the maximum in a group
    • topK() - Returns an array of the most frequent values in a group
    • topKWeighted() - Returns an array of the most frequent values in a group using weights
    • first_value() - Returns the first value in an ordered set of values within a partition
    • last_value() - Returns the last value in an ordered set of values within a partition

    New bit functions:

    • bitAnd() - Returns the bitwise AND of two expressions
    • bitCount() - Returns the number of bits set to one in the binary representation of a number
    • bitHammingDistance() - Returns the number of bits that differ between two numbers
    • bitNot() - Returns a number with all bits flipped
    • bitOr() - Returns the inclusive bitwise OR of two expressions
    • bitRotateLeft() - Rotates all bits in a number left by specified positions
    • bitRotateRight() - Rotates all bits in a number right by specified positions
    • bitShiftLeft() - Shifts all bits in a number left by specified positions
    • bitShiftRight() - Shifts all bits in a number right by specified positions
    • bitTest() - Returns the value of a specific bit in a number
    • bitXor() - Returns the bitwise exclusive-or of two expressions

    New mathematical functions:

    • abs() - Returns the absolute value of a number
    • log() - Computes the natural logarithm of a number
    • round() - Rounds a number to a specified number of decimal places
    • ceil() - Rounds a number up to the nearest integer
    • floor() - Rounds a number down to the nearest integer
    • pow() - Returns a number raised to the power of another number

    New string functions:

    • lowerUTF8() - Converts a string to lowercase using UTF-8 encoding
    • upperUTF8() - Converts a string to uppercase using UTF-8 encoding

    New encoding functions:

    • hex() - Converts a number to its hexadecimal representation
    • bin() - Converts a string to its binary representation

    New type conversion functions:

    • toUInt8() - Converts any numeric expression, or expression resulting in a string representation of a decimal, into an unsigned 8 bit integer

    Ready to get started?

    Whether you're building usage-based billing systems, customer analytics dashboards, or other custom analytics, these functions let you get the most out of your data. Get started with Workers Analytics Engine and explore all available functions in our SQL reference documentation.

  1. The GraphQL Analytics API now supports confidence intervals for sum and count fields on adaptive (sampled) datasets. Confidence intervals provide a statistical range around sampled results, helping verify accuracy and quantify uncertainty.

    • Supported datasets: Adaptive (sampled) datasets only.
    • Supported fields: All sum and count fields.
    • Usage: The confidence level must be provided as a decimal between 0 and 1 (e.g. 0.90, 0.95, 0.99).
    • Default: If no confidence level is specified, no intervals are returned.

    For examples and more details, see the GraphQL Analytics API documentation.

  1. New instance types provide up to 4 vCPU, 12 GiB of memory, and 20 GB of disk per container instance.

    Instance TypevCPUMemoryDisk
    lite1/16256 MiB2 GB
    basic1/41 GiB4 GB
    standard-11/24 GiB8 GB
    standard-216 GiB12 GB
    standard-328 GiB16 GB
    standard-4412 GiB20 GB

    The dev and standard instance types are preserved for backward compatibility and are aliases for lite and standard-1, respectively. The standard-1 instance type now provides up to 8 GB of disk instead of only 4 GB.

    See the getting started guide to deploy your first Container, and the limits documentation for more details on the available instance types and limits.

  1. You can now enhance your security posture by blocking additional application installer and disk image file types with Cloudflare Gateway. Preventing the download of unauthorized software packages is a critical step in securing endpoints from malware and unwanted applications.

    We have expanded Gateway's file type controls to include:

    • Apple Disk Image (dmg)
    • Microsoft Software Installer (msix, appx)
    • Apple Software Package (pkg)

    You can find these new options within the Upload File Types and Download File Types selectors when creating or editing an HTTP policy. The file types are categorized as follows:

    • System: Apple Disk Image (dmg)
    • Executable: Microsoft Software Installer (msix), Microsoft Software Installer (appx), Apple Software Package (pkg)

    To ensure these file types are blocked effectively, please note the following behaviors:

    • DMG: Due to their file structure, DMG files are blocked at the very end of the transfer. A user's download may appear to progress but will fail at the last moment, preventing the browser from saving the file.
    • MSIX: To comprehensively block Microsoft Software Installers, you should also include the file type Unscannable. MSIX files larger than 100 MB are identified as Unscannable ZIP files during inspection.

    To get started, go to your HTTP policies in Zero Trust. For a full list of file types, refer to supported file types.

  1. Users can now specify that they want to retrieve Cloudflare documentation as markdown rather than the previous HTML default. This can significantly reduce token consumption when used alongside Large Language Model (LLM) tools.

    Terminal window
    curl https://developers.cloudflare.com/workers/ -H 'Accept: text/markdown' -v

    If you maintain your own site and want to adopt this practice using Cloudflare Workers for your own users you can follow the example here.

  1. A new GA release for the Windows WARP client is now available on the stable releases downloads page.

    This release contains minor fixes and improvements.

    Changes and improvements

    • MASQUE is now the default tunnel protocol for all new WARP device profiles.
    • Improvement to limit idle connections in Gateway with DoH mode to avoid unnecessary resource usage that can lead to DoH requests not resolving.
    • Improvement to maintain TCP connections to reduce interruptions in long-lived connections such as RDP or SSH.
    • Improvements to maintain Global WARP override settings when switching between organizations.
    • Improvements to maintain client connectivity during network changes.

    Known issues

    • For Windows 11 24H2 users, Microsoft has confirmed a regression that may lead to performance issues like mouse lag, audio cracking, or other slowdowns. Cloudflare recommends users experiencing these issues upgrade to a minimum Windows 11 24H2 KB5062553 or higher for resolution.

    • Devices using WARP client 2025.4.929.0 and up may experience Local Domain Fallback failures if a fallback server has not been configured. To configure a fallback server, refer to Route traffic to fallback server.

    • Devices with KB5055523 installed may receive a warning about Win32/ClickFix.ABA being present in the installer. To resolve this false positive, update Microsoft Security Intelligence to version 1.429.19.0 or later.

    • DNS resolution may be broken when the following conditions are all true:

      • WARP is in Secure Web Gateway without DNS filtering (tunnel-only) mode.
      • A custom DNS server address is configured on the primary network adapter.
      • The custom DNS server address on the primary network adapter is changed while WARP is connected.

      To work around this issue, reconnect the WARP client by toggling off and back on.

  1. A new GA release for the macOS WARP client is now available on the stable releases downloads page.

    This release contains minor fixes and improvements.

    Changes and improvements

    • Fixed a bug preventing the warp-diag captive-portal command from running successfully due to the client not parsing SSID on macOS.
    • Improvements to maintain Global WARP override settings when switching between organizations.
    • MASQUE is now the default tunnel protocol for all new WARP device profiles.
    • Improvement to limit idle connections in Gateway with DoH mode to avoid unnecessary resource usage that can lead to DoH requests not resolving.
    • Improvements to maintain client connectivity during network changes.
    • The WARP client now supports macOS Tahoe (version 26.0).

    Known issues

    • macOS Sequoia: Due to changes Apple introduced in macOS 15.0.x, the WARP client may not behave as expected. Cloudflare recommends the use of macOS 15.4 or later.

    • Devices using WARP client 2025.4.929.0 and up may experience Local Domain Fallback failures if a fallback server has not been configured. To configure a fallback server, refer to Route traffic to fallback server.

  1. A new GA release for the Linux WARP client is now available on the stable releases downloads page.

    This release contains minor fixes and improvements including an updated public key for Linux packages. The public key must be updated if it was installed before September 12, 2025 to ensure the repository remains functional after December 4, 2025. Instructions to make this update are available at pkg.cloudflareclient.com.

    Changes and improvements

    Known issues

    • Devices using WARP client 2025.4.929.0 and up may experience Local Domain Fallback failures if a fallback server has not been configured. To configure a fallback server, refer to Route traffic to fallback server.
  1. Gateway users can now apply granular controls to their file sharing and AI chat applications through HTTP policies.

    The new feature offers two methods of controlling SaaS applications:

    • Application Controls are curated groupings of Operations which provide an easy way for users to achieve a specific outcome. Application Controls may include Upload, Download, Prompt, Voice, and Share depending on the application.
    • Operations are controls aligned to the most granular action a user can take. This provides a fine-grained approach to enforcing policy and generally aligns to the SaaS providers API specifications in naming and function.

    Get started using Application Granular Controls and refer to the list of supported applications.

  1. Radar now introduces Regional Data, providing traffic insights that bring a more localized perspective to the traffic trends shown on Radar.

    The following API endpoints are now available:

    All summary and timeseries_groups endpoints in HTTP and NetFlows now include an adm1 dimension for grouping data by first level administrative division (for example, state, province, etc.)

    A new filter geoId was also added to all endpoints in HTTP and NetFlows, allowing filtering by a specific administrative division.

    Check out the new Regional traffic insights on a country specific traffic page new Radar page.