Insider

Cloudflare fixes AI model vulnerability and resolves several technical outages

Between October 13 and October 27, Cloudflare reported a data leak in its GLM-5.3 AI model and experienced several service outages. A security incident affected 155 user responses due to a scheduler error. A separate outage on October 27 caused significant disruptions for HTTPS websites using external firewalls.

Verified against 8 archived primary sources · SHA-256 recorded Inspect sources & citations ↓
A silicon wafer with a grid of iridescent microchip dies under shallow focus
Photo by Laura Ockel on Unsplash
155
Responses affected
460
Job postings
30 minutes
Cache purge delay

Key points

  • From August 27 to September 9, 2026, a vulnerability in the GLM-5.3 model caused data leakage between users.
  • On October 27, the company recorded a major outage affecting clients whose traffic passes through external firewalls.
  • As of the end of the period, the company had 460 job postings for 436 unique positions.

Workers AI model data leak

From August 27 to September 9, 2026, a vulnerability in the GLM-5.3 model caused data leakage between users. Security researcher Gadi Evron found that the error occurred when requests exceeded the KV cache pool limit of 681,280 tokens. The SGLang scheduler incorrectly flagged rejected requests as active. This caused 155 responses to contain data from other users' previous requests.

After discovering the issue on September 9, Cloudflare set the model to private. The company updated configurations, patched SGLang, and modified its load balancer to prevent requests from being interrupted mid-transfer. The company continues to work with SGLang developers to fix similar memory-safety bugs in the architecture.

Service incidents

On October 27, the company recorded a major outage affecting clients whose traffic passes through external firewalls. Users observed ERR_TIMED_OUT errors on standard HTTPS websites and ERR_EMPTY_RESPONSE errors on non-standard ports.

Other technical issues occurred over the weekend of October 26-27. These included delayed or duplicated Workers Cron tasks, Workers Builds deployment errors, Access API hangs, cache purging delays of up to 30 minutes in EEUR, and degraded Cloudflare Stream performance for Western Europe.

Hiring

As of the end of the period, the company had 460 job postings for 436 unique positions. Most postings (350) offer a hybrid work format, 55 are distributed, and 42 are in-office.

Next steps

Investors should monitor SGLang security updates and stability reports for the Workers ecosystem. Since the vulnerability relates to a class of memory-safety bugs the company has been addressing for some time, service stability during complex network configurations remains a key metric for assessing operational risks.

Original sources

  1. Cross-request KV cache exposure in the GLM-5.3 Workers AI model, and our remediation with SGLangOctober 26, 2026SHA-256 of our archived copy 821e28068a55…
  2. Delayed, missed, and duplicated Workers Cron TriggersOctober 26, 2026SHA-256 of our archived copy d219b847e856…
  3. We are seeing some customers having issues with Workers BuildsOctober 27, 2026SHA-256 of our archived copy 4c9698ba2ed2…
  4. Elevated Cloudflare Access API ErrorsOctober 27, 2026SHA-256 of our archived copy 516a56bcf1be…
  5. Cache Purging Delays Affecting Requests Routed Through EEUROctober 27, 2026SHA-256 of our archived copy 23c65574972c…
  6. ERR_TIMED_OUT and ERR_EMPTY_RESPONSE being observed by Cloudflare CustomersOctober 27, 2026SHA-256 of our archived copy 2b24d3a23fb1…
  7. Cloudflare Stream performance issues impacting certain Live Broadcasts and On-Demand UploadsOctober 27, 2026SHA-256 of our archived copy 6894da32e344…
  8. Cloudflare, Inc. job board (greenhouse: cloudflare)SHA-256 of our archived copy f5c1ff6be263…
Cite this article

The fingerprint identifies the exact version of each original that the article was written from; the original stays at its source.

Prepared by AI from official company documents; automatic checks and an AI editor review it before publication, and not every article is read by a person. This is not investment advice. Editorial standards