cf-manager: SSRF via URL-based Worker deployment allows arbitrary code execution in victim Cloudflare accounts
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.
cf-manager is an all-in-one dashboard for managing multiple Cloudflare accounts and services. Prior to 1.1.2, worker/src/routes/workers.ts uses bare fetch(url) calls to retrieve user-supplied URLs and deploys the returned content as a Worker script using stored Cloudflare credentials. The multipart and JSON branches of POST /api/:accountId/workers and POST /api/batch-deploy accept URLs without protocol, destination, redirect, content-type, or response-size validation. An attacker with deployment API access, or unauthenticated access when API_SECRET is not configured, can make cf-manager access internal resources or fetch attacker-controlled JavaScript and execute it in the victim Cloudflare Workers account. This issue is fixed in version 1.1.2.
Briefing
Written from the sources below · deepseek-v4.1-flash
cf-manager prior to 1.1.2 uses bare fetch() on user-supplied URLs in its worker deployment routes without protocol, redirect, content-type, or size validation, allowing SSRF and deployment of attacker-controlled JavaScript. Users with deployment API access, or unauthenticated users when API_SECRET is not configured, are affected.
Why it mattersCVSS 10.0 critical: attackers can execute code in victim Cloudflare accounts via SSRF; EPSS is 0%, so no exploitation is known yet.
ActionUpgrade cf-manager to 1.1.2 and set API_SECRET to block unauthenticated deployment access.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| hefy2027 | <1.1.2 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket