Cloudflare patches a Magento zero-day while its developer tooling gets a v5 reset

A zero-day gets virtual patched at the edge

The week's most urgent item was defensive. Cloudflare's WAF shipped an emergency Managed Ruleset rule to block unauthenticated remote code execution in Adobe Commerce and Magento Open Source, a template-engine flaw tracked as CVE-2026-75650 and nicknamed "StyleSmuggler" that let attackers inject arbitrary PHP through style properties. Cloudflare is explicit that the edge rule is virtual patching only: origin applications still need Adobe's hotfix, and any exposed encryption keys, integration tokens, and system credentials should be rotated. If you run a Magento storefront, treat the WAF rule as time to patch, not a substitute for it.

Local Workers development gets a new shape

Miniflare v5 landed as the biggest developer-facing change of the week, realigning local Workers development with the forthcoming cf CLI and the cloudflare.config.ts programmatic config format. The release introduces a new configuration shape with breaking changes, removing deprecated and alpha D1 bindings and internal wrappedBindings APIs, dropping built-in module discovery, moving /cdn-cgi routes to /cdn-cgi/local, and replacing per-resource persistence options with shared persistence roots. Most projects sit behind wrangler dev, the Cloudflare Vite plugin, or the Vitest plugin and won't need to act directly, but anyone depending on Miniflare itself should plan for the migration.

The rest of the Workers toolchain churned steadily around it. Wrangler gained support for Durable Object-managed Containers via a durable_object scheduling policy, so namespace-backed Container applications are created after the Worker upload resolves the Durable Object namespace ID — a change mirrored in the deploy-helpers package. The same tooling got a meaningful performance pass: wrangler d1 execute --local no longer crawls on large SQL files, and wrangler dev stopped running custom build commands twice at startup, while a 64 MiB uncompressed bundle limit replaced the old gzip-based size checks and transient GET/HEAD failures no longer crash the dev server. Miniflare also picked up local simulation of Flagship bindings against a persisted store with an admin API for tests. Underneath, the runtime work was mostly plumbing: node:net gained a Server implementation and a connectHandler, and a sockets close() fix removed an uncaught exception when a pipe close was in flight. Python Workers now default to Python 3.14 for compatibility dates from 2026-09-08 onward.

Elsewhere on the platform, Browser Run added guardrails that restrict a session's requests to permitted hostnames, plus a read-only Live View mode, and Containers became a supported self-hosted execution environment for the OpenAI Agents API. AI Gateway got two billing-control refinements: a setting to require provider credentials and block Unified Billing fallback for BYOK providers, and cache-read and cache-write token rates in custom cost headers. Cloudflare One rounded things out with passive DLP detection that samples Gateway traffic before you commit to policies, per-login SAML reauthentication, and a CASB integration for Zoom. DNS users also now see warnings for shadowed records in every zone.

The AI SDK grows a harness layer and hardens its plumbing

Vercel's AI SDK spent the week expanding where agents can run and tightening security around how they authenticate. The headline addition is a GitHub Copilot harness adapter, letting harness users run agents inside the Copilot environment through the same HarnessAgent interface used by other targets, now also available as a standalone harness package and extended with native subscription authentication that keeps credentials at the host boundary. On the security side, a server-side request forgery fix in MCP OAuth metadata discovery rolled out across provider-utils and the MCP client. The SDK also added batch cancel and list APIs alongside a Cloudflare Workers atob compatibility fix, async tool calling and new GPT Image 2.5 quality options, and per-request batch models with enforced tool choices in streamText.

Vercel's own platform pushed breadth rather than depth. Sandbox doubled to 64 GB of storage and became available in every compute region with per-sandbox and failover region selection, while FastAPI frontends and static files are now served from the CDN without invoking a Function. Password Protection arrived per project on Pro at $20 a month, Connect let Pro and Enterprise teams restrict who manages connectors, and v0 added one-click Marketplace integrations for the likes of Resend, MongoDB Atlas, and Clerk. Tako Search went live on AI Gateway with free usage through September 30, and Vercel published a path for building OpenAI Agents API apps on Next.js and Functions.

Small but welcome, in the CLI and framework trenches

Railway's CLI kept shipping quality-of-life work: Codex remote clients and named config replay, OpenCode Desktop auto-configuration, embedded native clients defaulting harness launches to fresh VMs, and public domains on sandbox create and fork. Next.js canary work brought an experimental imgOptMozjpeg config and lazy Turbopack compilation of client dynamic imports. Beyond these, the collection absorbed a long tail of smaller patch releases across the same tools — nothing individually notable, but a reminder of how much quiet maintenance keeps the platforms moving.