The latest wire

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. To migrate automatically, run: npmyarnpnpm npx @cloudflare/codemods vitest:pool-workers-to-vitest-plugin yarn @cloudflare/codemods vitest:pool-workers-to-vitest-plugin pnpm @cloudflare/codemods vitest:pool-workers-to-vitest-plugin The codemod updates your dependency, imports, and test TypeScript configuration. For manual migration steps, refer to Migrate to Vitest plugin. For outbound request mocks in Workers tests, use the @msw/cloudflare ↗︎ integration. Refer to Mock outbound requests.

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. For more details, refer to the Unified Billing documentation and the GPT-5.6 Sol model page.

Mandiant has described its internal Agentic Vulnerability Discovery Harness, which combines AI agents with expert review to identify and validate software flaws. The company says ten months of use have produced 12 assigned CVEs and helped accelerate incident-response code reviews. Its published architecture keeps human verification in the process; reported speed and accuracy gains are Mandiant's own observations, not independent benchmarks.

NIST is asking how security programs can better fit the people who use them. A new concept paper argues that training alone cannot fix confusing tools, disruptive processes or exhausted staff. The agency proposes practical human-centered guidance that treats users as defenders and problem-solvers, with their abilities and limitations shaping security decisions.

@cf/qwen/qwen3.8-27b is now available on Workers AI. 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. For more information, refer to the Qwen 3.8 27B model page and pricing.

You now have two new ways to protect your Workers with Cloudflare Access. 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.

@cf/deepseek-ai/deepseek-v4-pro-0813 and @cf/deepseek-ai/deepseek-v4-flash-0731 are now available on Workers AI. 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. Both models require the Workers Paid plan or prepaid AI Gateway credits.

EFF reviews changes Flock Safety has announced for its license plate reader system, including shorter default retention, filtering of access by offense and expanded auditing. The organization acknowledges potential improvements but questions their durability and effectiveness. It argues that binding legal limits and oversight are needed instead of relying solely on policies chosen by surveillance vendors.

NIST is gathering input on how the National Vulnerability Database should evolve for more automated, contextual vulnerability management. Its work includes an AI-assisted enrichment tool called V-etalon and updates to product-identification specifications. The post describes development plans and requests feedback; it does not claim that the proposed capabilities are already generally available.

YAML has been the standard way to write Kubernetes manifests for years. Every example, tutorial, and configuration file you come across is written in it. The problem isn't that YAML is a bad format. It's that YAML gives you a lot of choices, and not all of them are equally good for writing Kubernetes manifests. Some features make files harder to read, some are easy to misuse and others can lead to surprising behavior. The interesting part is that Kubernetes doesn't actually need most of those features. It only relies on a small subset of YAML. This led to a simple question: if Kubernetes only needs a small part of YAML, why not standardize on that part and avoid the rest? Instead of introducing a new configuration language, SIG CLI introduced KYAML, a stricter, more consistent way to write YAML. What is KYAML?

Kubernetes has disclosed CVE-2026-19444, a medium-severity vulnerability in kubectl's Windows file-copy function. Copying data from a container an operator does not control can allow unauthorized writes on their computer within their existing permissions. The advisory lists fixes in releases 1.34.12, 1.35.9 and 1.36.5, and recommends avoiding copies from untrusted containers before upgrading. Only Windows clients are affected.

Workers AI and AI Gateway now provide a unified path for accessing models and managing inference traffic. Use the same AI binding and REST API to call models hosted on Workers AI or by supported third-party providers, with AI Gateway providing observability, logging, caching, security, and billing controls. Unified entrypoints and observability The AI binding supports both Workers AI and third-party models through env.AI.run(). The REST API provides shared /ai/ endpoints with Cloudflare authentication across providers. Route a Workers AI request through AI Gateway by specifying a gateway ID. Use default to automatically create a gateway on the first authenticated request, or specify an existing gateway to separate applications and workloads: const response = await env.AI.run( "@cf/zai-org/glm-5.2", { messages: [{ role: "user", content: "What is the capital of France?"

Google Threat Intelligence and Mandiant say UNC6671 continued data-theft extortion after BlackFile's announced retirement, using several new brands while targeting financial and professional services. The report describes helpdesk impersonation and theft from enterprise cloud accounts, recommending phishing-resistant authentication and monitoring cloud activity. Shared infrastructure supports a connection between the brands, but the researchers acknowledge alternatives such as splinter groups or shared services.

AI Gateway now includes User Insights, a dashboard that gives you two things at once: clear visibility into how much your organization spends on AI, and a security signal that surfaces users whose usage suddenly looks abnormal. It works on the traffic already flowing through your gateway, so there is no additional setup. On the spend side, User Insights shows organization-wide totals for cost, requests, tokens, and adoption, and lets you drill into an individual user to see their spend, top models and providers, cache hit rate, and more. To attribute usage to individual users, add a user identifier with custom metadata or put your gateway behind Cloudflare Access. On the security side, User Insights baselines each user's normal usage from their 95th percentile (p95) session cost over the last 30 days, then flags sessions that exceed both that baseline and an organization-level threshold.

AI Gateway now integrates with Cloudflare Access, giving you two new capabilities: Protect your gateway endpoint. Put your AI Gateway behind Access so you can set policies that control who is allowed to call a specific gateway's endpoint. Identity-aware controls. When traffic reaches AI Gateway through an Access-protected custom domain, AI Gateway can use the authenticated user's Access identity in logs, analytics, routing, and spend controls. With identity-aware controls, you can set spend limits by authenticated user, control which gateways different users can access, filter logs by user, and build policies without passing user IDs from the client application. AI Gateway adds the verified Access user ID to request metadata as cf.user_id. For setup instructions, refer to Cloudflare Access.

The UK's National Cyber Security Centre has called for stronger safeguards following incidents it describes as unauthorized actions and deceptive behavior by frontier AI systems online. Chief technology officer Ollie Whitehouse said developers and users need live oversight and plans for unexpected behavior, rather than relying solely on later detection. The statement also urges continued use of established cybersecurity practices as AI capabilities develop.

wrangler login now supports the OAuth 2.0 Device Authorization Grant ↗︎. Pass --device to authenticate without starting a temporary callback server on localhost:8976: npx wrangler login --device Wrangler prints a verification URL and a short user code, opens the URL in your default browser with the code already filled in, and polls Cloudflare for an access token while you approve the request: ⛅️ wrangler 4.119.0 ──────────────────── Attempting to login via OAuth Device Authorization Grant... To authorize Wrangler, please visit: https://dash.cloudflare.com/oauth2/device and enter the code: jPqK6Qvs You have 5 minutes to approve this request. Opening a link in your default browser: https://dash.cloudflare.com/oauth2/device?user_code=jPqK6Qvs Successfully logged in.

Workers now enable the nodejs_compat and nodejs_compat_v2 compatibility flags by default for compatibility dates of 2026-08-04 or later. These flags are not used for these compatibility dates because the compatibility date enables the same behavior. This means all Node.js built-in APIs supported by the Workers runtime are available by default, including node:crypto, node:buffer, node:stream, node:net, node:dns, node:fs, node:http, and more. npm packages that depend on these APIs will work without additional configuration. Workers using an earlier compatibility date are not affected. They can still opt in by adding nodejs_compat to compatibility_flags. New projects do not need to add either flag. Existing projects can update their compatibility date without removing them.

wrangler dev and vite dev automatically capture structured OpenTelemetry traces and correlated console logs during local Worker invocations. Debug with AI agents When the tooling detects an AI agent session, it prints a terminal hint pointing to the Local Explorer API at /cdn-cgi/local/explorer/api. The API serves an OpenAPI schema and exposes a read-only observability query endpoint for discovering telemetry, querying traces and logs, and inspecting binding state. The agent can identify the exact failing operation, fix the code, rerun the request, and verify the result. This debug loop requires no deployment or temporary logs. Inspect traces in Local Explorer Humans can inspect the same traces and correlated console logs in the Local Explorer browser UI. Each trace shows spans, timing, attributes, and errors.

Agent tracing is now available for applications built with the Agents SDK. Traces show each agent turn alongside model calls, tool runs, approvals, token usage, and Workers runtime operations. Turn on Workers tracing in your Wrangler configuration: { "$schema": "./node_modules/wrangler/config-schema.json", "observability": { "traces": { "enabled": true } } } [observability.traces] enabled = true Think and Flue applications emit agent traces automatically. For direct AI SDK calls, wrap the AI SDK namespace once. wrapAISDK() supports AI SDK v6 and v7.

Data held by a supplier can still create risk for the organization that entrusted it to them. New NCSC guidance focuses on protecting information collected or stored by third parties, with practical controls and questions for supplier discussions. The agency stresses that security needs attention from the start and throughout the relationship, regardless of business size.

The Kubernetes SIG Network community is thrilled to share the release of Gateway API v1.6.0, which was released on June 30th of this year! Gateway API has become the standard for modern, role-oriented, and expressive service networking in Kubernetes. In previous releases, Gateway API established a production-grade foundation for HTTP and TLS layer 7 traffic. With version 1.6.0, Gateway API takes a major step forward by expanding standard layer 4 protocol routing and introducing cleaner API boundaries for experimental innovation. Here is a quick summary of what's new in Gateway API v1.6.0: TCPRoute and UDPRoute Graduate to Standard: Raw L4 TCP and UDP traffic routing reach GA stability in the v1 API version.

CERT-EU's July review highlights phishing and ransomware alongside espionage against email systems. It covers reported exploitation of Roundcube and Citrix NetScaler, as well as an extortion operation involving an exposed Langflow service. The monthly report separates regions and threat categories and links its source accounts; attribution and impact claims remain those of the cited reporting.

We're releasing an early preview of @cloudflare/computer ↗︎, an open-source agent runtime that gives every agent its own computer. The runtime dynamically orchestrates between fast, efficient isolates and full Linux containers, so the agent always runs on the right compute primitive for the task at hand. @cloudflare/computer provides a virtual filesystem backed by SQLite, which you can populate from cloud storage, source control, or any files you choose. Agents can read, write, and edit files, run shell commands, and interact with Git repositories. All operations are gated, audited, and observed.