Skip to main content
Menu
CVEs

CVE

cf-manager remote code execution via Worker deploy

Affects cf-manager versions before 1.1.2 that deploy Workers from a user-supplied URL; the unauthenticated path applies only where API_SECRET is not configured. Fixed in 1.1.2.

CVE-2026-71499EUVD-2026-129147Published Updated Summary written by a model

10.0CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 1.1.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.1.2.

Summary

The cf-manager dashboard from hefy2027 has a server-side request forgery flaw in its URL-based Worker deployment. A remote attacker, without logging in, can make it fetch internal resources or attacker-controlled JavaScript and deploy that code as a Worker script that runs in the victim's Cloudflare account.

Original description

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.

Who should check

Teams running cf-manager before 1.1.2 that deploy Workers from URLs through the deployment API or batch-deploy, especially where API_SECRET is unset

“cf-manager's Worker deployment feature performs an unfettered fetch(url) on”

github.com

cve.now Index

30Pcve.now Index 30 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 10.0, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 35 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 1.1.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-71499 (cf-manager: SSRF via URL-based Worker deployment allows arbitrary code execution in victim Cloudflare accounts), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-71499 (entry last updated 2026-11-18):
Affected:
- hefy2027 cf-manager: fixed in 1.1.2
Fixed versions: 1.1.2.
Conditions (all must be true for the bug to be hit):
- cf-manager versions before 1.1.2 that use Worker deployment from a user-supplied URL (source: https://github.com/hefy2027/cf-manager/security/advisories/GHSA-wmx3-qxcc-mh64)
- Worker deployment with a URL through POST /api/:accountId/workers (multipart or JSON) or POST /api/batch-deploy (source: https://github.com/hefy2027/cf-manager/security/advisories/GHSA-wmx3-qxcc-mh64)
- The unauthenticated path applies only where API_SECRET is not configured (source: https://github.com/hefy2027/cf-manager/security/advisories/GHSA-wmx3-qxcc-mh64)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-71499 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-71499 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/hefy2027/cf-manager/security/advisories/GHSA-wmx3-qxcc-mh64
- https://github.com/hefy2027/cf-manager/commit/934aecbe614d8a08a8c96f393c0126519c35e3be
- https://github.com/hefy2027/cf-manager/releases/tag/1.1.2
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-71499
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-71499"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: total

  5. Record last updated

Affected versions

  • hefy2027 cf-manager

    fixed in 1.1.2

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · hefy2027/cf-manager · Advisory GHSA-wmx3-qxcc-mh64
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-71499
RecordNVD · CVE-2026-71499
Other links 2
RepositoryGitHub · hefy2027/cf-manager · Commit 934aecbe
RepositoryGitHub · hefy2027/cf-manager · Release 1.1.2

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-71499

Is CVE-2026-71499 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

cf-manager fetches a user-supplied URL during Worker deployment without restriction. An attacker can make it fetch attacker-controlled JavaScript and deploy it as a Worker script in the victim's Cloudflare account, effectively achieving remote code execution there.Source: github.com, github.com

Which versions are affected by CVE-2026-71499?

cf-manager: before 1.1.2.Source: cve.now feed data

Am I affected, and how do I check?

Versions before 1.1.2 that use Worker deployment from a URL, through POST /api/:accountId/workers (multipart or JSON) or POST /api/batch-deploy. The unauthenticated path applies only where API_SECRET is not configured, so check the installed version and whether API_SECRET is set.Source: github.com, github.com

How do I fix CVE-2026-71499?

Upgrade to cf-manager 1.1.2, which the advisory lists as the fixed version.Source: github.com, github.com

More CVEs