Cloudflare developer changelog

19 items in the render window (newest 100 + all corrections; not this source's all-time total) · status healthy · last successful fetch 2026-11-21 19:16 UTC
Feed for this sourceRSS
ACTION NEEDED APIDEPRECATIONMODEL Cloudflare developer changelog · 2026-11-21 19:18 UTC

Agents SDK v0.34.0 upgrades PiHarness to Pi 1.6, breaking backward compatibility

Do:Review the Pi Durable 1.6.0 changelog and Agents SDK v0.34.0 changelog for the full list of breaking changes.
WHAT CHANGEDCloudflare Agents SDK v0.34.0 upgrades PiHarness from Pi 1.5 to Pi 1.6. Once a conversation runs on Pi 1.6, Pi 1.5 cannot run its tool calls or model requests. API method signatures changed: harness.signal() replaces (await harness.pi()).signal(), and harness.root() must be called before reaching the root session through harness.pi(). A new error type MCPAuthorizationRequiredError is introduced for MCP re-authorization. The claudeCode() default model changed to claude-sonnet-5-5. Workers AI models were retired on November 20, 2026.
WHY IT MATTERSRolling back to Pi 1.5 after upgrading will break existing conversations that have run on Pi 1.6. Applications using the old signal delivery pattern or accessing the root session without calling harness.root() first will fail. MCP client implementations that do not catch the new error type will not handle re-authorization correctly.
WHAT TO DOReview the Pi Durable 1.6.0 changelog and Agents SDK v0.34.0 changelog for the full list of breaking changes. Update signal delivery calls from (await harness.pi()).signal() to harness.signal(). Add harness.root() calls before accessing the root session. Implement MCPAuthorizationRequiredError handling to redirect users to error.authUrl and provide a way to call reconnectMcpServer(id). Plan to roll forward rather than roll back if deployment issues occur.
Model-reported confidence 95% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Agents - Agents SDK now supports Pi 1.6 with tools that wait without keeping your agent awake
+https://developers.cloudflare.com/changelog/post/2026-11-20-pi-harness-pi-1-6/
+Fri, 20 Nov 2026 00:00:00 GMT
+
+Agents SDK v0.34.0 upgrades PiHarness to Pi 1.6 ↗︎. A Pi tool can now wait for a person, a deadline, or another session without keeping the Durable Object awake, and a session can start from a history that your application already has.
+Tools that wait
+
+Park until a signal or a deadline. A tool can return a park instead of a result, and Pi runs it again when a signal arrives or the deadline passes. While it waits, the call holds no invocation, so the Durable Object can hibernate. Deliver signals with the new harness.signal(). Refer to Tools that wait.
+Wait for a subagent. submit() and continue() take notify, so a parked tool wakes when another session's input settles. Refer to Wait for a subagent.
+Approval gates. A beforeTool hook can park a tool call before it runs, for example until a person approves it.
+
+Session updates
+
+Start a session from an existing history. harness.root(), sessions.create(), and sessions.fork() take Pi's init, which writes messages into the transcript in the commit that creates the session. The root session is now created on its first use, so harness.root() can seed it. Refer to Seed a session with an existing history.
+Keep queued input across an abort. With submit(input, { onAbort: "keep" }), stopping an answer does not drop the message that the user or another agent sent next.
+Steadier runs. Pi retries more dropped provider connections. When Anthropic can no longer continue a message thread, agents/models/pi-ai sends the whole conversation again instead of failing the turn. PiHarness.dispose() frees Pi AI's per-session state.
+
+Wait for a person's answer
+This tool asks the user a question, then parks until your agent delivers the answer:
+import { defineSignal } from "@earendil-works/pi-durable";
+import { obj, str } from "@earendil-works/pi-schema";
+
+const Answer = defineSignal({
+name: "app.answer",
+version: 1,
+schema: obj({ text: str() }),
+});
+
+const AskParameters = obj({ question: str() });
+
+const askUser = {
+name: "ask_user",
+description: "Ask the user a question and wait for the answer.",
+parameters: AskParameters,
+async execute({ question }, api, context) {
+const answer = await api.readSignal(Answer, "answer", context);
+if (answer !== undefined && "value" in answer) {
+return { output: [{ type: "text", text: answer.value.text }] };
+}
+await showQuestion(api.taskId, question);
+return { sleep: { signals: [Answer.key("answer")] } };
+},
+};
+
+// Later, in your agent, when the user answers:
+await this.harness.signal(taskId, Answer, "answer", { text: "Yes" });import {
+defineSignal,
+type ToolRegistration,
+} from "@earendil-works/pi-durable";
+import { obj, str } from "@earendil-works/pi-schema";
+
+const Answer = defineSignal({
+name: "app.answer",
+version: 1,
+schema: obj({ text: str() }),
+});
+
+const AskParameters = obj({ question: str() });
+
+const askUser: ToolRegistration<typeof AskParameters> = {
+name: "ask_user",
+description: "Ask the user a question and wait for the answer.",
+parameters: AskParameters,
+async execute({ question }, api, context) {
+const answer = await api.readSignal(Answer, "answer", context);
+if (answer !== undefined && "value" in answer) {
+return { output: [{ type: "text", text: answer.value.text }] };
+}
+await showQuestion(api.taskId, question);
+return { sleep: { signals: [Answer.key("answer")] } };
+},
+};
+
+// Later, in your agent, when the user answers:
+await this.harness.signal(taskId, Answer, "answer", { text: "Yes" });
+While the question is open, the session's run is still going, and the object can hibernate or be evicted. harness.signal() wakes the object, and Pi runs the tool again with the answer.
+Other changes
+
+MCP re-authorization. A request that needs the user to sign in again throws MCPAuthorizationRequiredError with a link. A failed server stays failed until you call the new reconnectMcpServer(id). Refer to Failures and reconnecting.
+Failed requests no longer send error details. A failed request gets a generic 500 response, and a failed WebSocket upgrade closes with code 1011. Use onFetchError() to choose the response. Refer to Failed requests.
+Chat fixes. Stop, clear, regenerate, and resume now work across tabs and during recovery.
+Scheduling fixes. A schedule, queue item, or Task run that is cancelled or replaced no longer runs again.
+Models. ai.image() and Pi AI's ai.images() run the FLUX.2 image models. claudeCode() defaults to claude-sonnet-5-5. Examples move off the Workers AI models retired on November 20, 2026.
+
+Upgrade
+Once a conversation runs on Pi 1.6, Pi 1.5 cannot run its tool calls or model requests. After upgrading, roll forward to fix deployment issues rather than rolling back to Pi 1.5.
+Deliver signals with harness.signal() instead of (await harness.pi()).signal(), and call harness.root() before you reach the root session through harness.pi(). If you use Pi Durable directly, RunEndTask is now HookTask, and code mode namespaces come from Extension.namespace. Refer to the Pi Durable 1.6.0 changelog ↗︎ for the full list of breaking changes.
+If you use the MCP client, catch MCPAuthorizationRequiredError and send the user to error.authUrl, and give users a way to call reconnectMcpServer(id) for a failed server. If you relied on error details in failed responses, implement onFetchError().
+The Agents SDK v0.34.0 changelog ↗︎ has step-by-step upgrade instructions. Point your coding agent at them and upgrade today:
+Copy promptPrompt copied!
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningBreaking API upgrade with incompatible session format, new error handling requirements, and model changes.
signalsbreaking API changes documented · model version upgrade (Pi 1.5 → Pi 1.6) · backward incompatibility warning · new SDK version (v0.34.0) · API method signature changes (harness.signal, harness.root) · new error type (MCPAuthorizationRequiredError) · deprecation of old patterns · model defaults changed (claudeCode → claude-sonnet-5-5) · Workers AI models retired date (November 20, 2026)
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING API Cloudflare developer changelog · 2026-11-21 07:10 UTC

Cloudflare Browser Run adds /script endpoint for single-request automation

Do:Review current Browser Run Worker deployments to identify automation that can move to /script endpoints.
WHAT CHANGEDCloudflare Browser Run introduced POST /script and POST /script/<sessionId> endpoints that execute Playwright, Puppeteer, or Chrome DevTools Protocol functions in a single API request without deploying a Worker. The endpoints return session and page identifiers in cf-browser-session-id and cf-browser-target-id response headers. Sessions remain open after script execution until explicitly closed with DELETE /devtools/browser/<sessionId> or until idle timeout. Workers can call the same endpoints through env.BROWSER.script() without an API token. A Script Studio interface in the Cloudflare dashboard allows writing and running scripts against live browsers without an API token.
WHY IT MATTERSExisting Browser Run workflows that deploy Workers for automation can now run the same code in a single API call, eliminating the deployment step. Sessions that are not explicitly closed will consume resources until idle timeout, changing the cleanup model from previous Browser Run usage patterns.
WHAT TO DOReview current Browser Run Worker deployments to identify automation that can move to /script endpoints. Add explicit session cleanup with DELETE /devtools/browser/<sessionId> or browser.close() calls to any new /script usage to avoid sessions running to idle timeout.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Browser Run - Run custom scripts in Browser Run with /script
+https://developers.cloudflare.com/changelog/post/2026-11-20-script-endpoint/
+Fri, 20 Nov 2026 00:00:00 GMT
+
+Browser Run now runs custom browser automation written with Playwright, Puppeteer, or the raw Chrome DevTools Protocol (CDP) in a single API request, with the new /script endpoints. Submit a JavaScript function, and Browser Run executes it in an isolated Worker connected to a browser session, so you do not need to deploy a Worker.
+curl -i -X POST "https://api.cloudflare.com/client/v4/accounts/<accountId>/browser-run/script" \
+-H "Authorization: Bearer <apiToken>" \
+-H "Content-Type: application/json" \
+-d '{
+"code": "async ({ page }) => { await page.goto(\"https://example.com\"); return { title: await page.title() }; }",
+"library": "playwright"
+}'
+HTTP/2 200
+content-type: application/json
+cf-browser-session-id: 8f7c2e3a-1b4d-4c6e-9a0f-2d5b7e9c1a3f
+cf-browser-target-id: A1B2C3D4E5F60718293A4B5C6D7E8F90
+
+{
+"success": true,
+"result": {
+"title": "Example Domain"
+}
+}
+
+POST /script acquires a browser, runs your function, and returns its result as { "success": true, "result": ... }. The session and page are returned in the cf-browser-session-id and cf-browser-target-id response headers (except Kitesurf runs).
+POST /script/<sessionId> runs follow-up scripts in a session you already hold, from /script or from POST /devtools/browser. Pass targetId to attach to a specific page, or create extra pages to run scripts concurrently in one session.
+Session launch options (keep_alive, recording, lab) go in the /script query string. Use browser=kitesurf to run a CDP script on Kitesurf.
+From a Worker, call the same endpoints through the browser binding with env.BROWSER.script(), without an API token.
+From the Cloudflare dashboard, write and run scripts against a live browser in Script Studio, without an API token.
+Neither endpoint closes the session after your script runs. Close it with DELETE /devtools/browser/<sessionId> or browser.close(). Otherwise, it ends at its idle timeout.
+
+For more information, refer to Custom scripts.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningNew API endpoints and execution model for Browser Run service materially expand platform capabilities.
signalsnew API endpoint introduced: POST /script · new endpoint variant: POST /script/<sessionId> · new response headers: cf-browser-session-id, cf-browser-target-id · new execution model: submit JavaScript function without deploying Worker · new query parameters: keep_alive, recording, lab, browser=kitesurf · new Worker binding method: env.BROWSER.script() · new dashboard feature: Script Studio · new session management: DELETE /devtools/browser/<sessionId>
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED APIDEPRECATION Cloudflare developer changelog · 2026-11-21 07:10 UTC

Cloudflare blocks dispatch namespace renames via API and CLI

Do:Audit your Terraform configurations, CI/CD pipelines, and operational scripts for dispatch namespace renames.
WHAT CHANGEDPUT and PATCH requests to the dispatch namespace API now return a 400 error with code 100413 if they attempt to change the name field. The wrangler dispatch-namespace rename command and Terraform cloudflare_workers_for_platforms_dispatch_namespace resource name changes fail with the same error. Cloudflare states this prevents failures where dispatch Workers and outbound Workers retained the old namespace name after a rename, causing subsequent API requests to read, deploy, or delete Workers to fail.
WHY IT MATTERSAny automation or infrastructure-as-code that renames dispatch namespaces will break. Terraform applies that change the name attribute will fail. Existing runbooks or scripts that use wrangler dispatch-namespace rename will stop working.
WHAT TO DOAudit your Terraform configurations, CI/CD pipelines, and operational scripts for dispatch namespace renames. Replace rename operations with the documented five-step migration: create new namespace, deploy user Workers to it, update dispatch Worker binding, verify routing, delete old namespace. Update any runbooks that reference wrangler dispatch-namespace rename.
Model-reported confidence 95% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Workers for Platforms - Dispatch namespaces can no longer be renamed
+https://developers.cloudflare.com/changelog/post/2026-11-20-dispatch-namespace-rename-removed/
+Fri, 20 Nov 2026 00:00:00 GMT
+
+You can no longer rename a dispatch namespace after creating it.
+Renaming a namespace could cause API requests to read, deploy, or delete Workers to fail because dispatch Workers and outbound Workers retained the namespace name they were deployed with. This change prevents those failures by rejecting rename requests.
+What changes:
+
+PUT and PATCH requests to the dispatch namespace API return a 400 error with code 100413 if they change name:
+Dispatch namespaces cannot be renamed. The name in the request must match the namespace's current name. To use a different name, create a new dispatch namespace.
+
+wrangler dispatch-namespace rename returns the same 100413 error.
+
+Terraform applies that attempt to change name on a cloudflare_workers_for_platforms_dispatch_namespace resource fail.
+
+To move your Workers to a namespace with a different name:
+
+Create a new dispatch namespace with the name you want.
+Deploy your user Workers to the new namespace.
+Update the dispatch namespace binding in your dispatch Worker to reference the new namespace, then redeploy the dispatch Worker.
+Verify that requests are routed to the new namespace and your Workers work as expected.
+Delete the user Workers in the old namespace, then delete the old namespace.
+
+For more information, refer to How Workers for Platforms works.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningBreaking API change removes rename capability; requires code and deployment changes.
signalsbreaking API change: PUT/PATCH requests now return 400 error · CLI tool behavior change: wrangler dispatch-namespace rename now fails · infrastructure-as-code impact: Terraform cloudflare_workers_for_platforms_dispatch_namespace resource affected · operational procedure required: multi-step workaround documented for namespace migration · error code introduced: 100413
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING APISECURITY Cloudflare developer changelog · 2026-11-21 07:10 UTC

Hyperdrive supports custom CA and mTLS over Workers VPC

Do:If you currently route Hyperdrive database traffic through Cloudflare Access and Tunnel to handle custom certificates, evaluate migrating to the VPC Service attachment m…
WHAT CHANGEDHyperdrive can now connect to private databases over Workers VPC using custom certificate authority (CA) certificates and client certificate authentication (mTLS). This covers PostgreSQL databases and Amazon RDS instances with private CA or RDS CA bundle certificates, and client certificates with RSA or EC P-256 keys. Certificates attach to the VPC Service, eliminating the previous requirement to route traffic through Cloudflare Access and Cloudflare Tunnel. Configuration requires Wrangler 4.164.0 or later, or Terraform provider 5.29.0 or later.
WHY IT MATTERSTeams connecting Hyperdrive to databases with custom certificates can remove the Access application, service token, and WebSocket handling previously required for this setup. The direct VPC connection simplifies the architecture and removes the Access layer from the database path.
WHAT TO DOIf you currently route Hyperdrive database traffic through Cloudflare Access and Tunnel to handle custom certificates, evaluate migrating to the VPC Service attachment method using the wrangler cert upload and wrangler vpc service create commands shown in the changelog.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Hyperdrive - Custom CA and mTLS certificates for Hyperdrive over Workers VPC
+https://developers.cloudflare.com/changelog/post/2026-11-18-hyperdrive-vpc-custom-ca-mtls/
+Wed, 18 Nov 2026 00:00:00 GMT
+
+Hyperdrive can now connect to private databases over Workers VPC with a custom certificate authority (CA) and client certificate authentication (mutual TLS, or mTLS). This covers PostgreSQL databases and Amazon RDS instances that present certificates signed by a private CA or the RDS CA bundle, and client certificates with RSA or EC P-256 keys.
+Previously, a database that required a custom CA or a client certificate meant routing database traffic over WebSockets through Cloudflare Access and Cloudflare Tunnel. That approach added an Access application, a service token, and WebSocket handling to maintain.
+Hyperdrive now connects directly to the database over Workers VPC, without Access.
+Attach the certificates to the VPC Service, then create a Hyperdrive configuration from that service:
+# Upload the private CA and the client certificate
+npx wrangler cert upload certificate-authority --ca-cert ./db-ca.pem --name db-ca
+npx wrangler cert upload mtls-certificate --cert ./client.pem --key ./client-key.pem --name db-client
+
+# Attach the certificates to the VPC Service for your database
+npx wrangler vpc service create my-postgres-db \
+--type tcp \
+--tcp-port 5432 \
+--app-protocol postgresql \
+--hostname <YOUR_DATABASE_HOSTNAME> \
+--tunnel-id <YOUR_TUNNEL_ID> \
+--certificate-authority <CA_CERTIFICATE_ID> \
+--client-certificate <CLIENT_CERTIFICATE_ID> \
+--cert-verification-mode verify_full
+
+# Create the Hyperdrive configuration from the VPC Service
+npx wrangler hyperdrive create <YOUR_CONFIG_NAME> \
+--service-id <YOUR_VPC_SERVICE_ID> \
+--database <DATABASE_NAME> \
+--user <DATABASE_USER> \
+--password <DATABASE_PASSWORD> \
+--scheme postgresql
+You can use a custom CA, a client certificate, or both. Configure VPC Services with Wrangler 4.164.0 or later, the API, or Terraform provider 5.29.0 or later. Dashboard support for these settings is not yet available.
+For setup details and certificate rotation, refer to Connect Hyperdrive to a private database using Workers VPC and Custom CA and client certificates.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew security and authentication capabilities for Hyperdrive enable direct database connections with mTLS and custom CA support, changing deployment patterns.
signalsnew capability added to existing service · authentication method expansion (mTLS support) · security feature (custom CA certificate support) · deployment workflow change (VPC Service attachment required) · tool version requirement specified (Wrangler 4.164.0+, Terraform 5.29.0+) · architectural simplification (removes Access/Tunnel requirement)
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED SECURITY Cloudflare developer changelog · 2026-11-20 20:24 UTC

CVE-2025-6087 SSRF vulnerability fixed in @opennextjs/cloudflare v1.3.0

Do:Update @opennextjs/cloudflare to v1.3.0 or later.
WHAT CHANGEDCloudflare published CVE-2025-6087 for an SSRF vulnerability in the @opennextjs/cloudflare package. The vulnerability is fixed in v1.3.0 and later versions.
WHY IT MATTERSSSRF vulnerabilities allow attackers to make the server perform requests to unintended destinations, potentially accessing internal resources or services that should not be externally reachable.
WHAT TO DOUpdate @opennextjs/cloudflare to v1.3.0 or later. Check your package.json and lock files for any version below v1.3.0.
Model-reported confidence 95% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 @opennextjs/cloudflare v1.2 released on June 5, 2025 delivers on these enhancements. By removing babel from the app code and dropping a dependency on @ampproject/toolbox-optimizer, we were able to reduce generated bundle sizes. Additionally, by stopping preloading of all app routes, we were able to improve the cold start time.
 This means that users will now see a decrease from 14 to 8MiB (2.3 to 1.6MiB gzipped) in generated bundle size for a Next app created via create-next-app, and typically 100ms faster startup times for their medium-sized apps.
 Users only need to update to the latest version of @opennextjs/cloudflare to automatically benefit from these improvements.
-Note that we published CVE-2005-6087 ↗︎ for a SSRF vulnerability in the @opennextjs/cloudflare package.
+We published CVE-2025-6087 ↗︎ for an SSRF vulnerability in the @opennextjs/cloudflare package.
 The vulnerability has been fixed from @opennextjs/cloudflare v1.3.0 onwards. Please update to any version after this one.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningSecurity vulnerability with explicit fix version; users must update to patch SSRF flaw.
signalssecurity vulnerability (CVE) disclosed · fixed version specified (v1.3.0) · actionable remediation required (update)
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED SECURITYAPI Cloudflare developer changelog · 2026-11-20 07:19 UTC

Cloudflare WAF adds CVE-specific rules for PHP and Ruby RCE vulnerabilities

Do:Check Cloudflare WAF logs for requests matching the new PHP-FPM (CVE-2026-129289) and PHP SOAP (CVE-2026-15353, CVE-2026-129506) rules.
WHAT CHANGEDCloudflare deployed WAF rules targeting CVE-2026-109618, CVE-2026-109619, CVE-2026-115560, CVE-2026-126714 (PHP RCE), CVE-2026-13282 (Ruby heap overflow), GHSA-87fm-7w84-j2px (Ruby integer overflow), CVE-2026-129289 (PHP-FPM), CVE-2026-15353 and CVE-2026-129506 (PHP SOAP). The PHP RCE rule detection was updated. New PHP-FPM and PHP SOAP rules default to log mode; all other new rules default to block mode.
WHY IT MATTERSApplications running vulnerable PHP or Ruby versions behind Cloudflare WAF are now protected by default against these remote code execution and overflow vulnerabilities. The PHP-FPM and SOAP rules log rather than block to reduce false positive risk, requiring manual review before enforcement.
WHAT TO DOCheck Cloudflare WAF logs for requests matching the new PHP-FPM (CVE-2026-129289) and PHP SOAP (CVE-2026-15353, CVE-2026-129506) rules. Override to block mode after confirming no false positives. Verify applications are not vulnerable to the listed CVEs.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## WAF - WAF Emergency Release - 2026-11-19
+https://developers.cloudflare.com/changelog/post/2026-11-19-emergency-waf-release/
+Thu, 19 Nov 2026 00:00:00 GMT
+
+This release introduces updates to an existing PHP Remote Code Execution rule to improve detection accuracy, as well as a few new generic, PHP and Ruby CVE specific rules. The new PHP rules are being deployed in log mode by default (in lieu of False Positive risk) and can be overridden after evaluating requests matching the rules. Supplementary information around the CVEs are available through Zero Wire phpAfterShell and six other PHP critical flaws ↗︎ and ruby2shell: heap overflow in Ruby string case conversion ↗︎.
+RulesetRule IDLegacy Rule IDDescriptionPrevious ActionNew ActionCommentsCloudflare Free Ruleset...7975ce1bN/APHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619, CVE-2026-115560, CVE-2026-126714) #6N/ABlockRule detection and description updated.Cloudflare Free Ruleset...b19210f1N/ARuby - Heap Overflow - CVE:CVE-2026-13282N/ABlockThis is a new detection.Cloudflare Free Ruleset...e9855f05N/ARuby - Integer Overflow - GHSA-87fm-7w84-j2pxN/ABlockThis is a new detection.Cloudflare Managed Ruleset...9d9c073dN/APHP Remote Code Execution Attack (CVE-2026-109618, CVE-2026-109619, CVE-2026-115560, CVE-2026-126714) #6N/ABlockRule detection and description updated.Cloudflare Managed Ruleset...34402c88N/ARuby - Heap Overflow - CVE:CVE-2026-13282N/ABlockThis is a new detection.Cloudflare Managed Ruleset...daf25922N/ARuby - Integer Overflow - GHSA-87fm-7w84-j2pxN/ABlockThis is a new detection.Cloudflare Managed Ruleset...6c6f42b2N/APHP-FPM - CVE:CVE-2026-129289N/ALogThis is a new detection.Cloudflare Managed Ruleset...a54028d4N/APHP SOAP - CVE:CVE-2026-15353N/ALogThis is a new detection.Cloudflare Managed Ruleset...4521b819N/APHP SOAP - CVE:CVE-2026-129506N/ALogThis is a new detection.Cloudflare Managed Ruleset...3f53db3cN/AGeneric Rules - Authentication BypassN/ABlockThis is a new detection.Cloudflare Managed Ruleset...36ba9f71N/AAnomaly - Embedded Application RequestN/ABlockThis is a new detection.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningEmergency WAF ruleset update with new CVE detections and rule action changes affecting security posture.
signalsfuture date: 2026-11-19 · emergency release designation · new WAF rules deployed · rule action changes: new rules set to Block or Log · PHP RCE rule detection updated · CVE-specific rules added · deployment mode specified: new PHP rules in log mode by default
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING API Cloudflare developer changelog · 2026-11-20 07:19 UTC

Cloudflare Images adds Gaussian sharpening mode with configurable parameters

Do:Review images currently using scalar sharpen values.
WHAT CHANGEDCloudflare Images sharpen parameter now accepts a structured object with mode=gaussian alongside amount (0-10), sigma (0-5), and optional threshold (0-255) settings. Existing scalar values like sharpen=5 continue using the box filter. The structured format works in URL parameters, Workers fetch() cf.image object, and Images binding .transform() calls.
WHY IT MATTERSGaussian sharpening provides finer control over edge detection for photography and complex images, reducing unwanted sharpening of noise or grain that box filtering treats uniformly. Different content types—text, product photos, illustrations—can now use tailored sharpening configurations instead of a single intensity value.
WHAT TO DOReview images currently using scalar sharpen values. For photography or content where box sharpening over-emphasizes grain, test Gaussian mode with amount and sigma settings appropriate to the content type. Update transform calls to use the structured object format if switching modes.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Cloudflare Images - Apply Gaussian sharpening with Images
+https://developers.cloudflare.com/changelog/post/2026-11-19-configurable-sharpening/
+Thu, 19 Nov 2026 00:00:00 GMT
+
+Cloudflare Images lets developers resize, adjust, and manipulate images at scale through a broad set of optimizations, including image adjustments such as sharpen, brightness, contrast, and gamma.
+The sharpen parameter now supports Gaussian sharpening, in addition to the existing box-filter sharpening. Sharpening makes fine details appear crisper by increasing the pixel-to-pixel contrast along edges, where adjacent pixels differ in brightness or color. Scalar values such as sharpen=5 continue to use the box filter.
+Different images benefit from different types and levels of sharpening. Text may need strong edge definition for readability; product photography often uses a subtler effect to avoid emphasizing grain; and illustrations with bold, clean lines and large areas of solid color can benefit from emphasizing larger edges and object outlines.
+Both box and Gaussian sharpening use unsharp masking, a technique that first creates a blurred version of the source image and subtracts it from the original to isolate edge details. Sharpening then adds a controlled amount of that detail back to the source along these boundaries, improving the perceived clarity of an image.
+Each filter uses a different method to produce the blur used for this comparison. The existing box filter produces a uniform blur by averaging each pixel with its eight surrounding pixels, weighing all nine equally. A Gaussian filter gives more weight to pixels closer to the center and provides more control to help prevent sharpening from treating unintended parts of an image as edges.
+Box sharpening offers a simple, predictable configuration for direct, crisp effects on text, screenshots, and simple graphics. Gaussian sharpening can produce smoother transitions for photography and offers more control over which details are emphasized.
+To use Gaussian sharpening, set the mode setting to gaussian, then configure its behavior using the additional amount, sigma, and threshold settings:
+
+Amount adjusts how strongly Images increases contrast around identified edges. It accepts values from 0 to 10.
+Sigma controls the spread of the Gaussian blur, which determines how far the sharpening effect extends around an edge. It accepts values greater than 0 and up to 5.
+Threshold (optional) excludes pixel differences below a specified value, which can reduce sharpening of low-contrast noise, grain, or smooth areas. It accepts integers from 0 to 255.
+
+Together, these settings let you tailor the sharpening effect to your content.
+In the URL interface, these settings are grouped beneath the sharpen parameter:
+sharpen=(mode=gaussian,amount=1,sigma=1.5,threshold=0)
+The same structure maps directly to the cf.image object in a Workers fetch() subrequest:
+cf: {
+image: {
+sharpen: {
+mode: "gaussian",
+amount: 1,
+sigma: 1.5,
+threshold: 0,
+},
+},
+}
+When using the Images binding, pass the structured sharpen object directly to .transform():
+const result = await env.IMAGES.input(source.body)
+.transform({
+sharpen: {
+mode: "gaussian",
+amount: 2,
+sigma: 1.5,
+threshold: 0,
+},
+})
+.output({ format: "image/avif" });
+
+return result.response();
+Refer to sharpen.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew image processing capability with API schema changes and new parameters developers must learn to use.
signalsnew API feature added: Gaussian sharpening mode for Images · new parameters introduced: mode, amount, sigma, threshold · API schema change: sharpen parameter now accepts structured object with mode setting · breaking change potential: existing scalar sharpen=N behavior preserved but new structured format available · execution change: developers must update code to use new Gaussian mode or continue with box filter
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED LIMITSAPI Cloudflare developer changelog · 2026-11-19 20:40 UTC

Cloudflare deletes Worker versions and Pages deployments after 30 days

Do:Audit CI/CD pipelines, documentation, and test suites for hardcoded Version URLs or Pages preview URLs.
WHAT CHANGEDCloudflare now deletes Worker versions and Pages deployments older than 30 days, except the 100 most recent versions and currently deployed versions. Deleted versions no longer appear in the dashboard or API, and their Version URLs and preview URLs stop working. Effective 19 November 2026.
WHY IT MATTERSAny automation, documentation, or testing that relies on Version URLs or Pages preview URLs older than 30 days will break. Rollback capability is limited to the 100 most recent versions instead of full history.
WHAT TO DOAudit CI/CD pipelines, documentation, and test suites for hardcoded Version URLs or Pages preview URLs. Replace Version URLs with Worker Previews for branch and pull request workflows, which always serve the latest deployment with production bindings.
ACT-BY DATE PASSED — this item's act-by date, 2026-11-19, is before this page was generated 2026-11-21 (UTC). Check the primary source before acting on it.
Model-reported confidence 95% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Workers, Pages - Workers and Pages now keep versions for 30 days
+https://developers.cloudflare.com/changelog/post/2026-11-19-workers-pages-version-retention/
+Thu, 19 Nov 2026 00:00:00 GMT
+
+Cloudflare now keeps versions of your Workers and deployments of your Pages projects for 30 days. After 30 days, they are deleted, except your 100 most recent and what is currently deployed.
+What is not affected:
+
+Running applications: Deployed Worker versions and your current Pages production deployment are always kept
+Rollbacks: You can still roll back to any of your 100 most recent Worker versions, and to any Pages production deployment that has not been deleted
+Worker Previews: Worker Preview URLs always serve the latest deployment of that Preview. Use Worker Previews for branches and pull requests instead of Version URLs, which run with your production bindings
+
+What you will notice:
+
+Deleted versions and deployments no longer appear in the dashboard or API
+The URL associated with each deleted Worker version, known as its Version URL (including any --preview-alias), stops working, as does the preview URL of each deleted Pages deployment
+
+For more information, refer to Workers version retention, Pages deployment limits, and Compare workflows.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.95, needed 0.5
triage reasoningNew retention policy with future effective date changes version URL availability and rollback limits for deployed applications.
signalsfuture date: 2026-11-19 · retention policy introduced: 30-day version retention · breaking change: version URLs stop working after 30 days · API change: deleted versions no longer appear in API · deployment limit: 100 most recent versions kept · rollback behavior change: limited to 100 most recent versions
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING API Cloudflare developer changelog · 2026-11-19 20:40 UTC

Browser Run /snapshot endpoint adds PDF, links, scrape, and JSON formats

Do:Review existing /snapshot calls.
WHAT CHANGEDCloudflare Browser Run's /snapshot endpoint now accepts four additional format values: pdf, links, scrape, and json. Previously /snapshot returned only HTML, screenshots, Markdown, and accessibility tree. The json format incurs Workers AI usage charges. Formats are captured in a fixed order regardless of array order, with PDF printed last. The actionTimeout budget (60s default, 120s max) now covers navigation, captures, retries, and AI requests. Requests must specify at least two distinct formats.
WHY IT MATTERSWorkflows that previously required multiple page loads to capture different formats (such as a PDF plus structured data) can now complete in a single request, reducing latency and Browser Run invocations. The json format adds Workers AI costs that were not present before. The fixed capture order and shared timeout budget change how multi-format requests behave under time pressure.
WHAT TO DOReview existing /snapshot calls. If you currently make separate requests for PDFs, links, scraped elements, or JSON extraction from the same page, consolidate them into one /snapshot call with multiple formats. For json format requests, add prompt or response_format as required and account for Workers AI usage in your budget. Verify that your actionTimeout settings accommodate the combined work of all requested formats.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Browser Run - Capture PDFs, links, scraped elements, and extracted JSON with /snapshot
+https://developers.cloudflare.com/changelog/post/2026-11-19-snapshot-all-formats/
+Thu, 19 Nov 2026 00:00:00 GMT
+
+Browser Run's /snapshot endpoint can now return four more formats from a single page load: pdf, links, scrape, and json. Before, /snapshot returned HTML, screenshots, Markdown, and the accessibility tree, so a workflow that also needed a PDF or structured data had to prepare the same page again in a second request.
+Use the new formats when you need to:
+
+PDF: print the page, with the same pdfOptions as the /pdf endpoint.
+Links: collect the links on the page, with the same visibleLinksOnly and excludeExternalLinks options as /links.
+Scraped elements: return the elements matched by elements, the same payload as /scrape. elements is required when you request it.
+Extracted JSON: extract structured data from the page HTML with Workers AI, with the same prompt, response_format, and custom_ai fields as /json. prompt or response_format is required, and the request incurs Workers AI usage.
+
+Request them through formats, the same way as the existing formats. This example returns a PDF, the page links, and the text of each paragraph:
+const response = await env.BROWSER.quickAction("snapshot", {
+url: "https://example.com/",
+formats: ["pdf", "links", "scrape"],
+elements: [{ selector: "p" }],
+});
+
+const { result } = await response.json();
+console.log(result.pdf);
+console.log(result.links);const response = await env.BROWSER.quickAction("snapshot", {
+url: "https://example.com/",
+formats: ["pdf", "links", "scrape"],
+elements: [{ selector: "p" }],
+});
+
+const { result } = await response.json();
+console.log(result.pdf);
+console.log(result.links);
+Formats are captured in a fixed order rather than the order of the formats array, and the PDF is printed last because print handlers can change the page. A live page can change between captures, and any format that fails fails the whole request. For JSON snapshots, one actionTimeout budget (default 60 seconds, maximum 120 seconds) covers navigation, captures, retries, and the AI request.
+You still need to request at least two distinct formats. If you only need one, use the corresponding single-format endpoint.
+Refer to the /snapshot documentation for the full list of accepted values and options.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew API capabilities, required fields, billing implications, and behavioral constraints affect integration and cost.
signalsnew endpoint capability: /snapshot now supports four additional formats (pdf, links, scrape, json) · API expansion: formats parameter now accepts new values · new required fields: elements required for scrape format, prompt or response_format required for json format · billing impact: json format incurs Workers AI usage charges · behavioral change: formats captured in fixed order, not array order; PDF printed last · constraint change: actionTimeout budget (60s default, 120s max) now covers navigation, captures, retries, and AI request · constraint: must request at least two distinct formats or use single-format endpoint
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING API Cloudflare developer changelog · 2026-11-19 20:40 UTC

Stream emits ERR_LIVE_INPUT_LLHLS_INCOMPATIBLE when B-frames detected in LL-HLS

Do:If you use Cloudflare Stream with Low-Latency HLS enabled, check your encoder settings and disable B-frames in your broadcast application.
WHAT CHANGEDCloudflare Stream now emits warning code ERR_LIVE_INPUT_LLHLS_INCOMPATIBLE once per live session when B-frames are detected in Low-Latency HLS broadcasts. The warning appears in the live input's Logs tab, live webhooks, and GraphQL input events. B-frames are not supported when LL-HLS is enabled for a live input.
WHY IT MATTERSB-frames in LL-HLS streams cause freezing and stuttering because they reference content not yet transmitted, stalling delivery preparation. The new warning surfaces a configuration error that degrades viewer experience but may have gone unnoticed without explicit detection.
WHAT TO DOIf you use Cloudflare Stream with Low-Latency HLS enabled, check your encoder settings and disable B-frames in your broadcast application. Alternatively, disable Low-Latency HLS in your live input settings if higher playback latency is acceptable.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Stream - B-frame detection for Low-Latency HLS live streams
+https://developers.cloudflare.com/changelog/post/2026-11-19-ll-hls-b-frame-warning/
+Thu, 19 Nov 2026 00:00:00 GMT
+
+Cloudflare Stream now emits a warning when B-frames are detected in Low Latency HLS live broadcasts.
+The most common cause of freezing and stuttering in LL-HLS live streams is when encoders include B-frames. These frames can reference content that has not yet been transmitted, stalling preparation for delivery. Therefore, B-Frames are not supported when LL-HLS is enabled for a live input.
+Stream sends the warning ERR_LIVE_INPUT_LLHLS_INCOMPATIBLE once per live session if applicable. It is reported alongside other error and status events in:
+
+Your live input's Logs tab
+Live webhooks
+GraphQL input events
+
+To resolve the warning, turn off B frames in your broadcast application settings. Alternatively, turn off Low-Latency HLS in your live input settings, but playback latency will be higher.
+For more information, refer to Stream live troubleshooting.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.78, needed 0.5
triage reasoningNew runtime warning and incompatibility constraint affects live stream encoding configuration and error handling.
signalsnew error code introduced: ERR_LIVE_INPUT_LLHLS_INCOMPATIBLE · breaking constraint: B-frames now incompatible with LL-HLS · new warning behavior: Stream now emits warnings on B-frame detection · integration impact: affects encoder configuration and live input setup · future date: 2026-11-19 indicates feature rollout
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED APISECURITY Cloudflare developer changelog · 2026-11-19 20:39 UTC

Workers VPC binding cf1:network now egresses through Gateway by default

Do:Review your Zero Trust DNS, HTTP, Network and egress policies in the Gateway dashboard.
WHAT CHANGEDWorkers using VPC Network binding with network_id: "cf1:network" now route public Internet egress through Cloudflare Gateway automatically. Previously this required Cloudflare Tunnel, Mesh, or WAN on-ramp; those are no longer required. Zero Trust traffic policies (DNS, HTTP, Network, and egress) now apply to Worker-originated traffic the same way they apply to WARP users.
WHY IT MATTERSExisting Zero Trust policies that were scoped to WARP users now also enforce on Worker egress traffic. If those policies block or filter traffic your Workers depend on, those Workers will fail. Gateway logs will now capture all Worker egress, changing what appears in audit trails and potentially what triggers alerts.
WHAT TO DOReview your Zero Trust DNS, HTTP, Network and egress policies in the Gateway dashboard. Verify none of them block hostnames or IP ranges your Workers with cf1:network bindings call. Check Gateway logs for new Worker egress entries and confirm they match expected behavior.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 Fri, 05 Jun 2026 00:00:00 GMT
 
 Workers using a VPC Network binding with network_id: "cf1:network" now egress to public Internet destinations through Cloudflare Gateway. This means your existing Zero Trust traffic policies — DNS, HTTP, Network, and egress — extend to traffic that originates from your Workers, the same way they do for WARP users today.
-WorkerCalls env.EGRESS.fetch()VPC binding↓Cloudflare MeshBind via cf1:network↓Cloudflare GatewayPolicies applied:DNSHTTPNetwork↓↗Public InternetAny public hostname or IPGateway logsDNSHTTPNetwork
+WorkerCalls env.EGRESS.fetch()VPC binding↓⇄VPC NetworkBind via cf1:networkNo Cloudflare Tunnel, Mesh, or WAN on-ramp required.↓Cloudflare GatewayPolicies applied:DNSHTTPNetwork↓↗Public InternetAny public hostname or IPGateway logsDNSHTTPNetwork
 What you get by default:
 
 Visibility. Worker egress shows up in Gateway DNS, HTTP, and Network logs alongside your other traffic, so you can audit what your Workers are calling and when.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningWorker egress routing and Zero Trust policy application fundamentally changed; existing deployments now subject to Gateway policies.
signalsdeployment architecture change: VPC binding egress routing modified · security/policy scope expansion: Zero Trust policies now apply to Worker egress · integration change: removal of Cloudflare Tunnel/Mesh/WAN requirement · behavioral change: traffic now flows through Cloudflare Gateway by default
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING SECURITYAPI Cloudflare developer changelog · 2026-11-18 20:36 UTC

Cloudflare Access adds automatic SAML IdP certificate retrieval

Do:If you use Cloudflare Access with SAML authentication, review the setup and emergency replacement guidance at the linked documentation to understand the revocation delay…
WHAT CHANGEDCloudflare Access can now retrieve SAML signing certificates from an identity provider's metadata endpoint. In the generic SAML configuration, set Signing certificate source to "Fetch certificates from IdP metadata" and provide the IdP metadata URL. For API configurations, use the metadata_url field instead of manual certificate fields. Access caches the certificates and does not poll the endpoint. Removing a compromised certificate from metadata does not immediately revoke the cached certificate or existing Access sessions.
WHY IT MATTERSAutomatic certificate retrieval eliminates manual certificate uploads when IdPs rotate signing certificates, but introduces a revocation delay risk. A compromised certificate removed from IdP metadata remains valid in Access's cache and does not terminate existing sessions, creating a window where revoked credentials continue to authenticate.
WHAT TO DOIf you use Cloudflare Access with SAML authentication, review the setup and emergency replacement guidance at the linked documentation to understand the revocation delay behavior before enabling automatic certificate discovery. For existing manual certificate configurations, no action is required unless you choose to migrate to the metadata_url approach.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Cloudflare One, Access - Automatically retrieve SAML IdP signing certificates
+https://developers.cloudflare.com/changelog/post/2026-11-18-saml-idp-certificate-discovery/
+Wed, 18 Nov 2026 00:00:00 GMT
+
+Cloudflare Access can retrieve signing certificates from a SAML identity provider's metadata endpoint. Your IdP can publish replacement certificates without requiring you to upload each one to Access.
+In your generic SAML identity provider configuration, set Signing certificate source to Fetch certificates from IdP metadata and enter the IdP metadata URL. The endpoint must return SAML metadata XML over public HTTPS, without authentication or redirects. It must not return a JSON Web Key Set (JWKS).
+For API configurations, use metadata_url instead of manual certificate fields:
+{
+"type": "saml",
+"config": {
+"issuer_url": "https://idp.example.com",
+"sso_target_url": "https://idp.example.com/sso",
+"metadata_url": "https://idp.example.com/metadata.xml"
+}
+}
+Access caches the certificates and does not poll the endpoint.
+Removing a compromised certificate from metadata does not immediately revoke the cached certificate or existing Access sessions. For setup, planned rotation, and emergency replacement guidance, refer to Discover IdP signing certificates.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.85, needed 0.5
triage reasoningNew SAML certificate discovery capability changes how teams configure and manage IdP authentication with Access.
signalsnew authentication feature added · API configuration change (metadata_url field introduced) · security-relevant behavior documented (certificate caching, revocation delay) · integration workflow change (automatic vs manual certificate management)
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED SECURITYAPI Cloudflare developer changelog · 2026-11-18 20:36 UTC

Cloudflare WAF adds 6 Java4Shell CVE-2026-114938 detections in log mode

Do:Review WAF logs for rule IDs 4d718bf4, 2337b51d, e5e5836c, 6fd6f152, 5a25d991, 67d74ebbN.
WHAT CHANGEDCloudflare deployed 6 new WAF rules targeting malformed base64 patterns associated with CVE-2026-114938 (Java4Shell). The rules detect malformed base64 in headers, query values, body values, path segments, JWT components, and WebAuthn values. All rules are deployed in log mode by default, not blocking mode.
WHY IT MATTERSApplications behind Cloudflare WAF will log but not block requests matching these patterns. If CVE-2026-114938 affects your Java components, you are collecting detection data but not preventing exploitation until you override the default action to block.
WHAT TO DOReview WAF logs for rule IDs 4d718bf4, 2337b51d, e5e5836c, 6fd6f152, 5a25d991, 67d74ebbN. If your application uses Java components vulnerable to CVE-2026-114938, override these rules to block mode following Cloudflare's blog post guidance.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## WAF - WAF Emergency Release - 2026-11-18
+https://developers.cloudflare.com/changelog/post/2026-11-18-emergency-waf-release/
+Wed, 18 Nov 2026 00:00:00 GMT
+
+This release introduces 6 new malformed base64 Cloudflare Managed Ruleset detections for Java4Shell CVE-2026-114938. The rules are being deployed in log mode by default (in lieu of False Positive risk) and can be overridden if needed with supplementary information around the same available through blog post How Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938) ↗︎.
+RulesetRule IDLegacy Rule IDDescriptionPrevious ActionNew ActionCommentsCloudflare Managed Ruleset...4d718bf4N/AJava4Shell - Malformed Base64 Header - CVE-2026-114938N/ALogThis is a new detection.Cloudflare Managed Ruleset...2337b51dN/AJava4Shell - Malformed Base64 Query Value - CVE-2026-114938N/ALogThis is a new detection.Cloudflare Managed Ruleset...e5e5836cN/AJava4Shell - Malformed Base64 Body Value - CVE-2026-114938N/ALogThis is a new detection.Cloudflare Managed Ruleset...6fd6f152N/AJava4Shell - Malformed Base64 Path Segment - CVE-2026-114938N/ALogThis is a new detection.Cloudflare Managed Ruleset...5a25d991N/AJava4Shell - Malformed Base64url JWT Component - CVE-2026-114938N/ALogThis is a new detection.Cloudflare Managed Ruleset...67d74ebbN/AJava4Shell - Malformed Base64 WebAuthn Value - CVE-2026-114938N/ALogThis is a new detection.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew WAF rules for Java4Shell CVE deployed in log mode; engineers must verify coverage and override settings.
signalsnew security rules deployed · CVE-specific detections added · future date (2026-11-18) · default log mode (non-blocking) · 6 new rule IDs in managed ruleset
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING SECURITYAPI Cloudflare developer changelog · 2026-11-18 07:32 UTC

Workers VPC adds custom CA and mTLS client certificate support

Do:If you connect Workers VPC to private certificate authorities or databases requiring client certificates, upload your CA and client certificates with wrangler cert uploa…
WHAT CHANGEDCloudflare Workers VPC Services now accept custom certificate authority (CA) certificates and client certificates for mutual TLS. Previously, Workers VPC trusted only publicly trusted CAs and Cloudflare Origin CA, requiring verify_ca or disabled modes to connect to private CAs, and could not reach origins requiring client certificates. Configuration requires Wrangler 4.164.0 or later, or Terraform provider 5.29.0 or later.
WHY IT MATTERSExisting Workers VPC connections to private CAs that use weakened verification modes (verify_ca or disabled) can now use full certificate verification. Services requiring mTLS, including PostgreSQL databases with Amazon RDS CA bundles, become reachable where they were not before.
WHAT TO DOIf you connect Workers VPC to private certificate authorities or databases requiring client certificates, upload your CA and client certificates with wrangler cert upload, reference them in VPC Service TLS settings, and set cert-verification-mode to verify_full to replace weakened verification.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Hyperdrive, Workers VPC - Custom CA and client certificates (mTLS) for Workers VPC
+https://developers.cloudflare.com/changelog/post/2026-11-18-custom-ca-mtls/
+Wed, 18 Nov 2026 00:00:00 GMT
+
+VPC Services can now verify private services that use certificates from your own certificate authority (CA), and authenticate to services that require mutual TLS (mTLS). Previously, Workers VPC only trusted publicly trusted CAs and Cloudflare Origin CA, so connecting to a private CA meant weakening verification with verify_ca or disabled, and origins that required client certificates were unreachable.
+Upload your CA certificate and client certificate, then reference them from the TLS settings of a VPC Service:
+npx wrangler cert upload certificate-authority --ca-cert ./ca.pem --name private-ca
+npx wrangler cert upload mtls-certificate --cert ./client.pem --key ./client-key.pem --name private-client
+
+npx wrangler vpc service create private-db \
+--type tcp \
+--tcp-port 5432 \
+--app-protocol postgresql \
+--hostname db.internal.example \
+--tunnel-id <TUNNEL_ID> \
+--certificate-authority <CA_CERTIFICATE_ID> \
+--client-certificate <CLIENT_CERTIFICATE_ID> \
+--cert-verification-mode verify_full
+You can use a custom CA, a client certificate, or both. The settings apply to HTTPS connections from http services and to TLS connections from tcp services, including PostgreSQL databases used with Hyperdrive, such as Amazon RDS instances that use the RDS CA bundle.
+You can configure custom CA and client certificates with Wrangler 4.164.0 or later, the API, or Terraform provider 5.29.0 or later.
+For details, refer to Custom CA and client certificates.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew mTLS and custom CA support removes prior workaround requirement and enables previously unreachable integrations.
signalsnew feature capability added · security/authentication enhancement · breaking change removal: previously required weakened verification (verify_ca or disabled) for private CAs, now supported natively · integration change: mTLS support for VPC Services · tool version requirement: Wrangler 4.164.0+, Terraform provider 5.29.0+ · future date: 18 Nov 2026
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED APIDEPRECATION Cloudflare developer changelog · 2026-11-17 20:59 UTC

Cloudflare CLI 1.0.0-rc.1 moves build output to v1 directory, renames commands

Do:Update scripts that capture cf output to read status messages from stderr.
WHAT CHANGEDCloudflare CLI 1.0.0-rc.1 moves Build Output to .cloudflare/output/v1/ and renames several API commands without aliases (e.g., cf workers secrets bulk becomes cf workers secrets bulk-edit). The release requires @cloudflare/vite-plugin 2.0.0-rc.0+ for Vite projects and Wrangler 4.163.0+ for legacy projects. Command output behavior changed: prompts and status messages now write to stderr, with stdout reserved for command output only.
WHY IT MATTERSScripts that parse cf command output will break if they read status messages from stdout instead of stderr. Automated workflows using renamed commands will fail without the new command names. Projects will fail to build if they use older versions of @cloudflare/vite-plugin or Wrangler than the new minimum requirements.
WHAT TO DOUpdate scripts that capture cf output to read status messages from stderr. Review the release notes for the complete list of renamed commands and update any automation or CI/CD pipelines that use them. Upgrade @cloudflare/vite-plugin to 2.0.0-rc.0+ or Wrangler to 4.163.0+ before updating cf.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Workers, Cloudflare CLI - Cloudflare CLI (cf) 1.0 release candidate
+https://developers.cloudflare.com/changelog/post/2026-11-17-release-candidate/
+Tue, 17 Nov 2026 00:00:00 GMT
+
+Cloudflare CLI (cf) 1.0.0-rc.1 is a release candidate for cf 1.0. cf has been in beta since late September. This is the release we recommend you try on your own projects, and we want your feedback before 1.0.
+To install or update to the latest release:
+npmyarnpnpmbunnpm install --global cf@latestyarn global add cf@latestpnpm add --global cf@latestbun add --global cf@latest
+What is stable
+We expect the following features to remain stable to cf 1.0:
+
+The cloudflare.config.ts configuration format.
+The Build Output format that cf build writes and cf deploy reads.
+The commands that create, develop, build, and deploy projects, including cf init, cf dev, cf build, cf deploy, cf previews deploy, and cf workers versions create.
+The large majority of commands generated from the Cloudflare API and used in the beta.
+
+A small number of less commonly used API commands may still change before 1.0. cf generates these commands from the Cloudflare API schema, so their call path may still change before 1.0.
+Upgrade from a beta
+This release moves Build Output to version 1, in .cloudflare/output/v1/. cf deploy will automatically create a new build on first run in this location.
+The release candidate also moves to caret (^) version ranges for its dependencies, requiring:
+
+@cloudflare/vite-plugin 2.0.0-rc.0 or later, for projects that build with Vite.
+Wrangler 4.163.0 or later, for legacy projects that build with Wrangler.
+
+1.0.0-rc.1 renames a few generated API commands without aliases. For example, cf workers secrets bulk is now cf workers secrets bulk-edit. For the full list, refer to the release notes ↗︎.
+If you last updated early in the beta, these earlier changes may also affect you:
+
+Prompts, progress, and status messages are written to stderr. Stdout holds only command output, so scripts that read messages from stdout must read stderr instead.
+Commands generated from camelCase or snake_case API names use kebab-case. For example, cf accounts billing getCredits is now cf accounts billing get-credits.
+cf previews deploy takes the Preview name as --preview-name instead of a positional argument.
+Commands run with --local store state in the project's .cloudflare/state directory.
+cf no longer saves your account choice between runs. Set accountId in cloudflare.config.ts or CLOUDFLARE_ACCOUNT_ID to skip the prompt.
+Streaming tail consumers move to experimental.streamingTailConsumers in cloudflare.config.ts.
+Destructive commands run without a terminal exit with an error unless you pass --force.
+cf supports the latest versions of the Node.js LTS releases and the latest active release of Node.js.
+
+Stream live logs
+cf observability tail streams live logs and other observability events as newline-delimited JSON. Select a Worker with --worker, a zone and its subdomains with --zone, or every event in the account with --all. Narrow the results with --filters, as inline JSON or from a file:
+cf observability tail --worker my-worker
+cf observability tail --worker my-worker --filters @filters.json
+Worker events require Workers Logs to be turned on for the Worker. For filter shapes and examples, run cf observability tail --help.
+What changed during the beta
+Deploy
+
+Deploy a directory of static assets with cf deploy ./dist. cf skips the build step and creates an assets-only Worker.
+cf deploy --no-provision fails when a binding has no resource ID, instead of creating a new resource.
+cf deploy --force deploys when the Worker was last deployed through the API, or when its remote configuration conflicts with your local Build Output.
+Redeploying no longer removes secrets that you added outside cloudflare.config.ts.
+Stack traces from deployed Workers show project paths such as src/index.ts.
+Python Workers with vendored packages deploy correctly.
+cf deploy applies SSH settings for Containers managed by Durable Objects.
+cf deploy --dry-run shows the project setup changes it would make, without making them.
+Set CLOUDFLARE_DEPENDENCIES_INSTRUMENTATION=false to stop uploading package dependency metadata with each deployment.
+
+Develop
+
+cf init creates new Worker projects with Vite+, including checks, formatting, and tests that run in the Workers runtime.
+cf dev and cf build run the Vite or Vite+ executable installed in your project, including dependencies hoisted in a workspace.
+cf dev passes arguments such as --port and --host to your framework's development server.
+cf dev --profile <name> passes the selected authentication profile to your development server.
+cf dev, cf build, and cf deploy offer to run cf migrate when they find a Wrangler configuration file.
+On Windows, Ctrl+C exits cleanly when your framework runs through npm, Wrangler and Vite start without spawn EFTYPE errors, and cf d1 migrations create rejects names that Windows cannot store.
+cf init approves the build scripts that pnpm 11 and later block by default, so installation succeeds.
+
+Sign in and accounts
+
+Pass --temporary-account to create a short-lived account without signing in. cf prints a URL you can use to claim the account.
+cf auth login summarizes the scopes you granted, and cf auth scopes lists them by product.
+cf auth whoami, also available as cf whoami, prints a short summary in a terminal and full JSON for scripts and agents.
+cf auth login now uses the system keyring where available.
+Long-running commands, such as cf observability tail, refresh an expired OAuth login instead of failing.
+cf auth whoami reports the status of scoped API tokens correctly.
+Set CLOUDFLARE_API_HEADERS to send custom headers with API requests.
+
+API commands
+
+Every command accepts --dry-run to preview what it would do and it redacts sensitive fields in request previews.
+cf checks --body input before it asks you to sign in or confirm, and rejects array bodies larger than the API allows instead of splitting them across several requests.
+More request fields are available as flags, including JSON objects and maps, arrays of objects, and file uploads. For example, cf pages deployments create --worker-js @./_worker.js and cf ai to-markdown --files @first.html @second.pdf.
+Error outputs have been improved with additional messages the API returns, such as the names of missing parameters.
+cf workers commands accept --worker to select a Worker.
+--zone finds zones by name in accounts with many zones.
+cf tunnels quick-start --allowed-mail limits a temporary tunnel to the email addresses and domains you allow.
+
+Scripts and agents
+
+cf --version prints only the version number.
+Shell completions and cf tools list every flag a command accepts.
+cf cli search has reranked cf deploy and other key commands to improve their ranking for static site and Pages deployment searches.
+cf docs search finds Cloudflare documentation from the terminal.
+
+Send feedback
+To report a bug or tell us what is missing, open an issue in the cf repository ↗︎. For every change in each release, refer to the Cloudflare CLI release notes ↗︎.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningRelease candidate with breaking changes, new dependency floors, and config format migrations affecting deployment workflows.
signalsrelease candidate announcement with future 1.0 GA implied · breaking API changes documented (command renames, argument structure changes) · dependency version floor changes (Wrangler 4.163.0+, @cloudflare/vite-plugin 2.0.0-rc.0+) · build output format migration (v1 directory structure change) · configuration format changes (cloudflare.config.ts structure shifts) · stderr/stdout behavior change affecting script integration · authentication and state management changes (no account persistence, keyring support)
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING APIPRICING Cloudflare developer changelog · 2026-11-17 20:59 UTC

AI Search adds optional file summarization during indexing

Do:If you update AI Search instances programmatically, include the current value of every indexing_options field in update calls to prevent unintended resets.
WHAT CHANGEDCloudflare AI Search can now generate summaries, topics, and keywords for indexed text documents that produce at least three chunks. Enable by setting indexing_options.file_summary to true in the dashboard or API when creating or updating an instance. The feature is off by default, and changing the setting triggers a full reindex.
WHY IT MATTERSLLM summarization costs are billed separately as Workers AI usage, not covered by the AI Search ingestion allotment. Each new or modified file is summarized once, so costs scale with indexed content volume. Updating indexing_options replaces all options as a whole; omitted options revert to defaults.
WHAT TO DOIf you update AI Search instances programmatically, include the current value of every indexing_options field in update calls to prevent unintended resets. If you enable file summaries, forecast the additional Workers AI costs based on your indexing volume.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## AI Search - AI Search can generate file summaries during indexing
+https://developers.cloudflare.com/changelog/post/2026-11-17-file-summaries/
+Tue, 17 Nov 2026 00:00:00 GMT
+
+AI Search can now summarize your files while it indexes them. For each text document that produces at least three chunks, AI Search uses a large language model (LLM) to generate a summary, topics, and keywords:
+
+The summary and keywords are stored in the item's context metadata. A context value you already set is kept.
+The topics are added to the context header of the file's chunks to help retrieval.
+
+Turn on file summaries in the dashboard, or set indexing_options.file_summary to true when you create or update an instance. File summaries are off by default, and changing the setting triggers a full reindex.
+indexing_options is replaced as a whole on every update. Include the current value of every option, or the options you leave out return to their defaults.
+The LLM costs are billed to your account. File summaries are not part of the AI Search ingestion allotment. AI Search uses a Workers AI model suited to summarization and calls it through your instance's AI Gateway, or the default gateway if none is set, and the calls are billed as Workers AI usage. Each new or modified file is summarized once, so costs grow with the amount of content you index.
+For more information, refer to File summaries.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew billable feature with separate cost model and API parameter changes affecting indexing behavior and billing.
signalsnew feature with billing implications · new API parameter (indexing_options.file_summary) · explicit cost model change: LLM summarization billed separately from ingestion allotment · behavioral change: full reindex triggered by setting change · data handling change: metadata and context enrichment during indexing
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
WORTH KNOWING API Cloudflare developer changelog · 2026-11-17 20:59 UTC

Cloudflare One Appliance HA sites can now configure separate WAN gateways per appliance

Do:If you operate Cloudflare One Appliance HA sites and want each appliance on a separate ISP circuit, add static_addressing.secondary_gateway_address to your WAN configura…
WHAT CHANGEDCloudflare One Appliance high availability sites can now assign each appliance its own default gateway on a static WAN. The API accepts a new optional field static_addressing.secondary_gateway_address in PATCH requests to /accounts/{account_id}/magic/sites/{site_id}/wans/{wan_id}. The dashboard adds a Secondary gateway address field next to Primary gateway address when configuring static WANs on HA sites. If omitted or set to null, the secondary appliance uses the primary gateway address, matching previous behavior.
WHY IT MATTERSHA pairs can now connect each appliance to a separate ISP circuit with its own static IP and gateway, enabling true dual-circuit redundancy instead of sharing a single WAN gateway. Existing HA configurations continue working unchanged because the field defaults to the primary gateway when not specified.
WHAT TO DOIf you operate Cloudflare One Appliance HA sites and want each appliance on a separate ISP circuit, add static_addressing.secondary_gateway_address to your WAN configuration API calls or populate the Secondary gateway address field in the dashboard. No action required if your HA pairs share a single WAN gateway.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Cloudflare One Appliance, Cloudflare One, Cloudflare WAN - Configure a separate WAN gateway for each appliance in a high availability site
+https://developers.cloudflare.com/changelog/post/2026-11-17-appliance-ha-secondary-gateway/
+Tue, 17 Nov 2026 00:00:00 GMT
+
+You can now give each Cloudflare One Appliance in a high availability (HA) site its own default gateway on a static WAN. Before this change, both appliances in an HA pair shared the same WAN gateway. Now each appliance can connect to its own Internet circuit, such as a different ISP for each appliance, with its own static IP and gateway.
+
+In the dashboard, when you configure a static WAN on an HA site, enter the secondary appliance's gateway in the new Secondary gateway address field, next to Primary gateway address.
+In the API, set static_addressing.secondary_gateway_address when you create or update a WAN. To remove the value with a PATCH request, set it to null.
+
+The field is optional. If you leave it blank, the secondary appliance uses the primary gateway address, which matches how HA sites worked before. You can only use this field on sites in HA mode.
+curl --request PATCH \
+https://api.cloudflare.com/client/v4/accounts/{account_id}/magic/sites/{site_id}/wans/{wan_id} \
+--header "Authorization: Bearer <API_TOKEN>" \
+--header "Content-Type: application/json" \
+--data '{
+"static_addressing": {
+"address": "203.0.113.2/30",
+"gateway_address": "203.0.113.1",
+"secondary_address": "198.51.100.2/30",
+"secondary_gateway_address": "198.51.100.1"
+}
+}'
+For details, refer to About high availability configurations.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew API field and HA configuration capability changes how teams deploy dual-appliance sites.
signalsnew API field introduced: static_addressing.secondary_gateway_address · breaking change to HA site behavior: secondary appliance gateway now configurable · API schema expansion: PATCH request now accepts secondary_gateway_address parameter · deployment model change: each appliance can now use separate ISP circuits · backward compatibility preserved: field optional, defaults to primary gateway if omitted
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
ACTION NEEDED API Cloudflare developer changelog · 2026-11-17 20:59 UTC

Cloudflare Email API uses 'address' field in REST, 'email' in Workers

Do:If you call the Cloudflare Email REST API, change recipient field names from 'email' to 'address'.
WHAT CHANGEDThe REST API for Cloudflare Email now uses 'address' as the field name for recipient email addresses, while the Workers binding continues to use 'email'. Both accept an optional 'name' field for display names on to, cc, bcc, replyTo, and from.
WHY IT MATTERSCode calling the REST API directly with the 'email' field will fail or send incorrectly. Workers binding calls are unaffected, creating a divergence between the two interfaces to the same service.
WHAT TO DOIf you call the Cloudflare Email REST API, change recipient field names from 'email' to 'address'. Workers binding code requires no change.
Model-reported confidence 95% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
 https://developers.cloudflare.com/changelog/post/2026-05-28-named-email-recipients/
 Thu, 28 May 2026 00:00:00 GMT
 
-You can now send emails with display names on recipient addresses in addition to the existing from support. Pass an object with email and an optional name field for to, cc, bcc, replyTo, or from:
+You can now send emails with display names on recipient addresses in addition to the existing from support. With the Workers binding, pass an object with email and name fields for to, cc, bcc, replyTo, or from. With the REST API, the object uses address and an optional name:
 src/index.jsjsexport default {
 async fetch(request, env) {
 const response = await env.EMAIL.send({
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.85, needed 0.5
triage reasoningBreaking API change to REST endpoint field naming and structure for email recipients.
signalsAPI contract change: REST API now uses 'address' field instead of 'email' · binding-specific behavior documented: Workers binding vs REST API divergence · field requirement change: 'name' field behavior differs between implementations
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)
Corrections and arithmetic notes
CORRECTED Cloudflare Workers Builds runtime defaults updated across Node.js, Python, Ruby, Go, Bun
CORRECTED 2026-10-18 23:27 UTC — [CORRECTION · WHAT CHANGED] Original: “Poetry 2.0.7→2.1.4” Fact: The source lists Poetry 2.1.3→2.4.3, and also pipx 1.7.1→1.17.2, which the item left out. / Checked against the Cloudflare changelog entry on 2026-10-18.
Cloudflare developer changelog · published 2026-10-16 16:42 UTC · corrected 2026-10-18 23:27 UTC · stood 54h 44m · cause extraction error
WHAT CHANGED (CORRECTED)Cloudflare Workers Builds changed default runtime versions effective 14 October 2026: Node.js 24.18.0→24.21.0, Python 3.13.3→3.14.8, Ruby 3.4.7→3.4.11, Go 1.24.3→1.27.2, Bun 1.2.15→1.4.3, Yarn 4.9.1→4.18.1, pip 25.1.1→26.2.1, pipx 1.7.1→1.17.2, Poetry 2.1.3→2.4.3, uv 0.7.13→0.12.10. Projects without explicit version pinning now build with these newer versions. Override environment variables are now documented: NODE_VERSION, PYTHON_VERSION, RUBY_VERSION, GO_VERSION, BUN_VERSION, YARN_VERSION.
Original text (as first published, superseded)
WHAT CHANGEDCloudflare Workers Builds changed default runtime versions effective 14 October 2026: Node.js 24.18.0→24.21.0, Python 3.13.3→3.14.8, Ruby 3.4.7→3.4.11, Go 1.24.3→1.27.2, Bun 1.2.15→1.4.3, Yarn 4.9.1→4.18.1, pip 25.1.1→26.2.1, Poetry 2.0.7→2.1.4, uv 0.7.13→0.12.10. Projects without explicit version pinning now build with these newer versions. Override environment variables are now documented: NODE_VERSION, PYTHON_VERSION, RUBY_VERSION, GO_VERSION, BUN_VERSION, YARN_VERSION.
Full item and evidence ↗