What is the CVSS score of CVE-2026-11325?

CVE-2026-11325 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.5%.

Which versions of Cloudflare pages-action are affected by CVE-2026-11325?

The deprecated Cloudflare pages-action GitHub Action contains a critical remote code execution vulnerability enabling exfiltration of CI/CD secrets including Cloudflare API tokens and GitHub tokens…

How to fix or mitigate CVE-2026-11325?

Within 24 hours: audit all GitHub Actions workflows to identify usage of cloudflare/pages-action and immediately rotate all CLOUDFLARE_API_TOKEN and GITHUB_TOKEN values created before the vulnerability discovery date. Within 7 days: migrate all affected CI/CD pipelines to supported alternatives (evaluate Cloudflare's native GitHub integration or direct API-based deployment) and remove all references to cloudflare/pages-action across repositories and branches. Within 30 days: complete credential rotation validation, audit historical workflow execution logs for evidence of unauthorized exfiltration, and establish preventive controls to restrict use of archived GitHub Actions.

Cloudflare pages-action CVE-2026-11325

EUVD-2026-57178 HIGH

OS Command Injection (CWE-78)

2026-08-12 cloudflare

GHSA-7f69-cxp9-gxx9

RCE Command Injection Cloudflare Https

8.8

CVSS 3.1 · Vendor: cloudflare

Severity by source

Vendor (cloudflare) PRIMARY

8.8 HIGH

AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

vuln.today AI

8.8 HIGH

Network-delivered via PR, no attacker privileges needed, but maintainer must trigger the workflow run (UI:R); secrets compromise yields full C/I/A impact within runner scope.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (cloudflare).

CVSS VectorVendor: cloudflare

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Aug 12, 2026 - 12:22 vuln.today

CVE Published

Aug 12, 2026 - 11:31 cve.org

HIGH 8.8

DescriptionCVE.org

Description

Cloudflare was recently notified by external researchers of vulnerabilities in this archived repository, including a remote code execution issue in src/index.ts reachable from certain GitHub Actions workflow configurations. Successful exploitation may expose workflow secrets such as CLOUDFLARE_API_TOKEN and GITHUB_TOKEN to an attacker. Because this repository has been deprecated since 2024, Cloudflare will not be issuing patches. To remediate this issue, we recommend migrating to cloudflare/wrangler-action immediately. Consumers who have already migrated are not affected.

Sunset Date

The cloudflare/pages-action repository will be removed on 2026-09-18. Consumers must complete migration before 18th September to avoid CI disruption.

Affected Versions

All published versions of cloudflare/pages-action, including consumers pinned to the v1 moving tag.

Patched Versions

None. This repository will not receive further updates, including security patches.

Resolution / Migration Path Migrate all workflows using cloudflare/pages-action to cloudflare/wrangler-action before 2026-09-18. Refer to the wrangler-action README for the equivalent step configuration and migration guidance.

Credit

Thanks to @agentka99 and @beg1nn3r for reporting their findings via Cloudflare's HackerOne program that informe

AnalysisAI

Remote code execution in the archived Cloudflare pages-action GitHub Action (src/index.ts) allows network-adjacent attackers to exfiltrate CI/CD secrets - including CLOUDFLARE_API_TOKEN and GITHUB_TOKEN - from affected workflow runner environments. All published versions of cloudflare/pages-action are affected, and Cloudflare has confirmed no patch will be issued because the repository has been deprecated since 2024 and is scheduled for removal on 2026-09-18. No public exploit code has been confirmed at time of analysis, but the vulnerability was discovered and reported through Cloudflare's HackerOne program by external researchers.

Technical ContextAI

The affected component is cloudflare/pages-action, a GitHub Actions step used to deploy to Cloudflare Pages directly from CI/CD pipelines. The root cause is classified as CWE-78 (OS Command Injection), meaning user-controlled input - likely derived from GitHub event context such as PR metadata, branch names, or commit messages - reaches a shell execution path in src/index.ts without adequate sanitization. In GitHub Actions, this class of flaw is commonly exploitable when workflows process pull_request or pull_request_target events from forks, allowing external contributors to inject shell metacharacters that are passed to runtime commands. The CPE string (cpe:2.3:a:cloudflare:https://github.com/cloudflare/pages-action:*:*:*:*:*:*:*:*) and affected-versions listing confirm all releases, including consumers pinned to the v1 floating tag, are in scope.

RemediationAI

No vendor-released patch identified at time of analysis, and Cloudflare has confirmed none will be issued. The sole supported remediation path is migration from cloudflare/pages-action to cloudflare/wrangler-action before 2026-09-18, after which the repository will be deleted and any remaining consumers will experience CI/CD breakage. Migration guidance is available in the wrangler-action README at https://github.com/cloudflare/wrangler-action. As an immediate compensating control prior to migration, organizations should audit all workflows using pages-action and restrict the workflow triggers to avoid processing untrusted external input (e.g., disable pull_request_target events from forks, or gate workflow execution on maintainer approval). Additionally, rotate any CLOUDFLARE_API_TOKEN and GITHUB_TOKEN secrets exposed to pages-action workflows if there is any suspicion of prior exploitation, as these tokens would have been accessible to an attacker who triggered the RCE. Pinning to a specific commit SHA rather than the v1 floating tag does not address the underlying vulnerability but limits exposure to unreviewed upstream changes.