Cloudflare Release Notes
Last updated: Feb 13, 2026
Cloudflare Products (12)
- Analytics30 release notes
- Application Performance18 release notes
- Application Security47 release notes
- Cloudflare AI31 release notes
- Cloudflare One42 release notes
- Consumer Services8 release notes
- Core Platform43 release notes
- Developer Platform72 release notes
- Docs Collections19 release notes
All Cloudflare Release Notes (361)
- Feb 12, 2026
- Date parsed from source:Feb 12, 2026
- First seen by Releasebot:Feb 13, 2026
Docs Collections by Cloudflare
Introducing Markdown for Agents
Cloudflare adds real time HTML to Markdown conversion at the edge for enabled zones via content negotiation. AI agents can request text/markdown and receive formatted Markdown from Cloudflare's network on the fly. This accelerates AI processing and reduces token usage.
Cloudflare's network now supports real-time content conversion at the source, for enabled zones using content negotiation headers. When AI systems request pages from any website that uses Cloudflare and has Markdown for Agents enabled, they can express the preference for text/markdown in the request: our network will automatically and efficiently convert the HTML to markdown, when possible, on the fly.
Here is a curl example with the Accept negotiation header requesting this page from our developer documentation:
curl \ https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/ \ -H "Accept: text/markdown"The response to this request is now formatted in markdown:
HTTP/2 200 date : Wed, 11 Feb 2026 11:44:48 GMT content-type : text/markdown; charset=utf-8 content-length : 2899 vary : accept x-markdown-tokens : 725 content-signal : ai-train=yes, search=yes, ai-input=yes --- title : Markdown for Agents Cloudflare Agents docs ---What is Markdown for Agents
Markdown has quickly become the lingua franca for agents and AI systems as a whole. The format's explicit structure makes it ideal for AI processing, ultimately resulting in better results while minimizing token waste.
...
Refer to our developer documentation and our blog announcement for more details.
Original source Report a problem - Feb 12, 2026
- Date parsed from source:Feb 12, 2026
- First seen by Releasebot:Feb 12, 2026
Cloudflare Fundamentals - Introducing Markdown for Agents
Cloudflare now converts HTML to Markdown on the fly for enabled zones when clients request text/markdown. This real time content negotiation delivers Markdown formatted docs automatically.
Cloudflare's network now supports real-time content conversion at the source, for enabled zones using content negotiation headers. When AI systems request pages from any website that uses Cloudflare and has Markdown for Agents enabled, they can express the preference for text/markdown in the request: our network will automatically and efficiently convert the HTML to markdown, when possible, on the fly.
Here is a curl example with the Accept negotiation header requesting this page from our developer documentation:
curl https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/ \ -H "Accept: text/markdown"The response to this request is now formatted in markdown:
Original source Report a problemHTTP/2 200 date: Wed, 11 Feb 2026 11:44:48 GMT content-type: text/markdown; charset=utf-8 content-length: 2899 vary: accept x-markdown-tokens: 725 content-signal: ai-train=yes, search=yes, ai-input=yes --- title: Markdown for Agents · Cloudflare Agents docs --- ### What is Markdown for Agents Markdown has quickly become the lingua franca for agents and AI systems as a whole. The format’s explicit structure makes it ideal for AI processing, ultimately resulting in better results while minimizing token waste. ... Refer to our developer documentation and our blog announcement for more details. All of your release notes in one place
Join Releasebot and get updates from Cloudflare and hundreds of other software products.
- Feb 12, 2026
- Date parsed from source:Feb 12, 2026
- First seen by Releasebot:Feb 12, 2026
Consumer Services by Cloudflare
Content Type Dimension for AI Bots in Cloudflare Radar
Radar now brings content type insights for AI bot and crawler traffic with a new content_type dimension and filter. Access MIME type distributions via API endpoints and per-bot content type in Verified Bots and AI Bots datasets. See it on the AI Insights page.
Content type insights
Radar now includes content type insights for AI bot and crawler traffic. The new content_type dimension and filter shows the distribution of content types returned to AI crawlers, grouped by MIME type category.
The content type dimension and filter are available via the following API endpoints:
◦ /ai/bots/summary/content_type◦ /ai/bots/timeseries_groups/content_type
Content type categories:
- HTML - Web pages (text/html)
- Images - All image formats (image/*)
- JSON - JSON data and API responses (application/json, *+json)
- JavaScript - Scripts (application/javascript, text/javascript)
- CSS - Stylesheets (text/css)
- Plain Text - Unformatted text (text/plain)
- Fonts - Web fonts (font/, application/font-)
- XML - XML documents and feeds (text/xml, application/xml, application/rss+xml, application/atom+xml)
- YAML - Configuration files (text/yaml, application/yaml)
- Video - Video content and streaming (video/*, application/ogg, *mpegurl)
- Audio - Audio content (audio/*)
- Markdown - Markdown documents (text/markdown)
- Documents - PDFs, Office documents, ePub, CSV (application/pdf, application/msword, text/csv)
- Binary - Executables, archives, WebAssembly (application/octet-stream, application/zip, application/wasm)
- Serialization - Binary API formats (application/protobuf, application/grpc, application/msgpack)
- Other - All other content types
Additionally, individual bot information pages ↗ now display content type distribution for AI crawlers that exist in both the Verified Bots and AI Bots datasets.
Original source Report a problem
Check out the AI Insights page ↗ to explore the data. - Feb 12, 2026
- Date parsed from source:Feb 12, 2026
- First seen by Releasebot:Feb 12, 2026
Content Type Dimension for AI Bots in Cloudflare Radar
Radar now shows content type insights for AI bot and crawler traffic, introducing a content_type dimension and filters. Access distributions by MIME category via new API endpoints and bot pages for AI crawlers.
Radar now includes content type insights
Radar now includes content type insights for AI bot and crawler traffic. The new content_type dimension and filter shows the distribution of content types returned to AI crawlers, grouped by MIME type category.
The content type dimension and filter are available via the following API endpoints
- /ai/bots/summary/content_type
- /ai/bots/timeseries_groups/content_type
Content type categories
- HTML - Web pages (text/html)
- Images - All image formats (image/*)
- JSON - JSON data and API responses (application/json, *+json)
- JavaScript - Scripts (application/javascript, text/javascript)
- CSS - Stylesheets (text/css)
- Plain Text - Unformatted text (text/plain)
- Fonts - Web fonts (font/, application/font-)
- XML - XML documents and feeds (text/xml, application/xml, application/rss+xml, application/atom+xml)
- YAML - Configuration files (text/yaml, application/yaml)
- Video - Video content and streaming (video/*, application/ogg, *mpegurl)
- Audio - Audio content (audio/*)
- Markdown - Markdown documents (text/markdown)
- Documents - PDFs, Office documents, ePub, CSV (application/pdf, application/msword, text/csv)
- Binary - Executables, archives, WebAssembly (application/octet-stream, application/zip, application/wasm)
- Serialization - Binary API formats (application/protobuf, application/grpc, application/msgpack)
- Other - All other content types
Additionally, individual bot information pages ↗ now display content type distribution for AI crawlers that exist in both the Verified Bots and AI Bots datasets.
Check out the AI Insights page ↗ to explore the data.
Original source Report a problem - February 2026
- No date parsed from source.
- First seen by Releasebot:Feb 11, 2026
Application Security by Cloudflare
Security Center - Enhanced Logo Matching for Brand Protection
Brand Protection upgrades logo matching with a redesigned model and UI. New configurable match thresholds, visible visual match scores, and direct logo previews in the Cloudflare dashboard to speed triage and expose impersonators.
We have significantly upgraded our Logo Matching capabilities within Brand Protection. While previously limited to approximately 100% matches, users can now detect a wider range of brand assets through a redesigned matching model and UI.
What’s new
- Configurable match thresholds: Users can set a minimum match score (starting at 75%) when creating a logo query to capture subtle variations or high-quality impersonations.
- Visual match scores: Allow users to see the exact percentage of the match directly in the results table, highlighted with color-coded lozenges to indicate severity.
- Direct logo previews: Available in the Cloudflare dashboard — similar to string matches — to verify infringements at a glance.
Key benefits
- Expose sophisticated impersonators who use slightly altered logos to bypass basic detection filters.
- Faster triage of the most relevant threats immediately using visual indicators, reducing the time spent manually reviewing matches.
- Ready to protect your visual identity? Learn more in our Brand Protection documentation.
- February 2026
- No date parsed from source.
- First seen by Releasebot:Feb 11, 2026
Enhanced Logo Matching for Brand Protection
Brand Protection unveils a major Logo Matching upgrade with a redesigned model and UI. New configurable thresholds from 75%, visible visual match scores, and direct logo previews in the Cloudflare dashboard speed triage and catch subtle impersonations.
What’s new
- Configurable match thresholds: Users can set a minimum match score (starting at 75%) when creating a logo query to capture subtle variations or high-quality impersonations.
- Visual match scores: Allow users to see the exact percentage of the match directly in the results table, highlighted with color-coded lozenges to indicate severity.
- Direct logo previews: Available in the Cloudflare dashboard — similar to string matches — to verify infringements at a glance.
Key benefits
- Expose sophisticated impersonators who use slightly altered logos to bypass basic detection filters.
- Faster triage of the most relevant threats immediately using visual indicators, reducing the time spent manually reviewing matches.
Ready to protect your visual identity? Learn more in our Brand Protection documentation.
Original source Report a problem - Feb 11, 2026
- Date parsed from source:Feb 11, 2026
- First seen by Releasebot:Feb 11, 2026
Developer Platform by Cloudflare
Workers - Workers are no longer limited to 1000 subrequests
Cloudflare Workers now remove the old 1000 subrequest cap, enabling more fetch calls per request. Paid plans can raise subrequests up to 10 million via Wrangler config, while free plans stay capped at 50 external and 1000 Cloudflare service subrequests. You can also set lower limits.
Subrequests limits
Workers no longer have a limit of 1000 subrequests per invocation, allowing you to make more fetch() calls or requests
to Cloudflare services on every incoming request. This is especially important for long-running Workers requests, such as
open websockets on Durable Objects or long-running Workflows, as these could often exceed this limit and error.By default, Workers on paid plans are now limited to 10,000 subrequests per invocation, but this
limit can be increased up to 10 million by setting the new subrequests limit in your Wrangler configuration file.wrangler.jsonc
{ "limits": { "subrequests": 50000, }, }wrangler.toml
[limits] subrequests = 50_000Workers on the free plan remain limited to 50 external subrequests and 1000 subrequests to Cloudflare services per invocation.
To protect against runaway code or unexpected costs, you can also set a lower limit for both subrequests and CPU usage.
wrangler.jsonc
{ "limits": { "subrequests": 10, "cpu_ms": 1000, }, }wrangler.toml
[limits] subrequests = 10 cpu_ms = 1_000For more information, refer to the Wrangler configuration documentation for limits and subrequest limits.
Original source Report a problem - Feb 11, 2026
- Date parsed from source:Feb 11, 2026
- First seen by Releasebot:Feb 11, 2026
Developer Platform by Cloudflare
Workers - Improved React Server Components support in the Cloudflare Vite plugin
Cloudflare's Vite plugin now integrates with the official @vitejs/plugin-rsc for React Server Components, adding a childEnvironments option to run multiple environments inside one Worker. This enables the parent to import modules from a child environment for a typical RSC setup.
The Cloudflare Vite plugin integration
The Cloudflare Vite plugin now integrates seamlessly @vitejs/plugin-rsc, the official Vite plugin for React Server Components.
A childEnvironments option has been added to the plugin config to enable using multiple environments within a single Worker.
The parent environment can then import modules from a child environment in order to access a separate module graph.
For a typical RSC use case, the plugin might be configured as in the following example:
export default defineConfig({ plugins: [ cloudflare({ viteEnvironment: { name: "rsc", childEnvironments: ["ssr"], }, }), ], });@vitejs/plugin-rsc provides the lower level functionality that frameworks, such as React Router, build upon.
The GitHub repository includes a basic Cloudflare example.
Original source Report a problem - Feb 10, 2026
- Date parsed from source:Feb 10, 2026
- First seen by Releasebot:Feb 11, 2026
Application Security by Cloudflare
WAF - WAF Release - 2026-02-10
Release notes
This week’s release changes the rule action from BLOCK to Disabled for Anomaly:Header:User-Agent - Fake Google Bot.
Ruleset
- Cloudflare Managed Ruleset
- ce11be543594412bb4bb92516aa0bef8
- N/A
- Anomaly:Header:User-Agent - Fake Google Bot
- Enabled
- Disabled
- We are changing the action for this rule from BLOCK to Disabled
- Feb 10, 2026
- Date parsed from source:Feb 10, 2026
- First seen by Releasebot:Feb 5, 2026
- Modified by Releasebot:Feb 11, 2026
Application Security by Cloudflare
WAF - WAF Release - Scheduled changes for 2026-02-16
Release Records
Zimbra - Local File Inclusion - CVE:CVE-2025-68645
- Announcement Date: 2026-02-10
- Release Date: 2026-02-16
- Release Behavior: Log
- Legacy Rule ID: N/A
- Rule ID: a219dd28a0694faea0f942d4b0089874
- Description: Zimbra - Local File Inclusion - CVE:CVE-2025-68645
- Comments: This is a new detection.
Vite - WASM Import Path Traversal - CVE:CVE-2025-31125
- Announcement Date: 2026-02-10
- Release Date: 2026-02-16
- Release Behavior: Log
- Legacy Rule ID: N/A
- Rule ID: b10164cf42ab47b7ab274b9573b09f52
- Description: Vite - WASM Import Path Traversal - CVE:CVE-2025-31125
- Comments: This is a new detection.