CVE-2026-3125: @opennextjs/cloudflare Opennextjs-cloudflare Has SSRF Vulnerability Vulnerability
HIGHCVE-2026-3125 is a HIGH opennextjs-cloudflare has ssrf vulnerability vulnerability (CWE-706: Use of Incorrectly-Resolved Name or Reference) affecting @opennextjs/cloudflare libraries in the npm ecosystem. The issue involves opennextjs-cloudflare has ssrf vulnerability via /cdn-cgi/ path normalization bypass. Remediation is available by upgrading affected packages to version 1.17.1.
CVE-2026-3125 at a Glance
How to Fix CVE-2026-3125
To remediate this vulnerability, upgrade all affected @opennextjs/cloudflare dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @opennextjs/cloudflare@1.17.1
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @opennextjs/cloudflare
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-3125, inspect your project dependencies using npm:
npm ls @opennextjs/cloudflare
Analyze the terminal output to locate any version of @opennextjs/cloudflare in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.17.1), your application is affected.
Note: The npm ls @opennextjs/cloudflare command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-706: Use of Incorrectly-Resolved Name or Reference, where the product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere. In @opennextjs/cloudflare, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-3125 Affected @opennextjs/cloudflare Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@opennextjs/cloudflare
|
npm |
< 1.17.1
|
1.17.1
|
References
Frequently Asked Questions
What is CVE-2026-3125?
Which @opennextjs/cloudflare versions are affected?
What version fixes CVE-2026-3125?
Is @opennextjs/cloudflare affected?
What CWE is associated with CVE-2026-3125?
How can I check npm dependencies for CVE-2026-3125?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-c7mq-gh6q-6q7c",
"modified" : "2026-03-05T00:57:07Z",
"published" : "2026-03-05T00:57:07Z",
"aliases" : [ "CVE-2026-3125" ],
"summary" : "opennextjs-cloudflare has SSRF vulnerability via /cdn-cgi/ path normalization bypass",
"details" : "A Server-Side Request Forgery (SSRF) vulnerability was identified in the @opennextjs/cloudflare package, resulting from a path normalization bypass in the /cdn-cgi/image/ handler.\n\nThe @opennextjs/cloudflare worker template includes a /cdn-cgi/image/ handler intended for development use only. In production, Cloudflare's edge intercepts /cdn-cgi/image/ requests before they reach the Worker. However, by substituting a backslash for a forward slash (/cdn-cgi\\image/ instead of /cdn-cgi/image/), an attacker can bypass edge interception and have the request reach the Worker directly. The JavaScript URL class then normalizes the backslash to a forward slash, causing the request to match the handler and trigger an unvalidated fetch of arbitrary remote URLs.\n\nFor example: https://victim-site.com/cdn-cgi\\image/aaaa/https://attacker.com\n\nIn this example, attacker-controlled content from attacker.com is served through the victim site's domain (victim-site.com), violating the same-origin policy and potentially misleading users or other services.\n\nNote: This bypass only works via HTTP clients that preserve backslashes in paths (e.g., curl --path-as-is). Browsers normalize backslashes to forward slashes before sending requests.\n\nAdditionally, Cloudflare Workers with Assets and Cloudflare Pages suffer from a similar vulnerability. Assets stored under /cdn-cgi/ paths are not publicly accessible under normal conditions. However, using the same backslash bypass (/cdn-cgi\\... instead of /cdn-cgi/...), these assets become publicly accessible. This could be used to retrieve private data. For example, Open Next projects store incremental cache data under /cdn-cgi/_next_cache, which could be exposed via this bypass.\n\n### Impact\n\n- SSRF via path normalization bypass of Cloudflare edge interception\n- Arbitrary remote content loading under the victim site's domain\n- Same-origin policy bypass\n- Potential for infrastructure abuse (scanning from Cloudflare IP space, worker resource exhaustion)\n- Exposure of private assets stored under /cdn-cgi/ paths. For example, Open Next projects store incremental cache data under /cdn-cgi/_next_cache, which could be exposed via this bypass.\n\n### Credits\n\nDisclosed responsibly by security researcher @Ezzer17.\n\n### Mitigations\n\nThe following mitigations have been put in place:\n\nServer-side updates to Cloudflare's Workers platform to block backslash path normalization bypasses for /cdn-cgi requests. The update automatically mitigates the issue for all existing and any future sites deployed to Cloudflare Workers.\n\nIn addition to the platform level fix, [Root cause fix](https://github.com/opennextjs/opennextjs-cloudflare/pull/1147) has been implemented to the Cloudflare adapter for Open Next. The patched version of the adapter is found at @opennextjs/cloudflare@1.17.1 (https://www.npmjs.com/package/@opennextjs/cloudflare)\n\n[Dependency update](https://github.com/opennextjs/opennextjs-cloudflare/pull/1150) to the Next.js template used with create-cloudflare (c3) to use the fixed version of the Cloudflare adapter for Open Next. Despite the automatic mitigation deployed on Cloudflare's platform, we encourage affected users to upgrade to the patched version of @opennextjs/cloudflare.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:H/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@opennextjs/cloudflare"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.17.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/opennextjs/opennextjs-cloudflare/security/advisories/GHSA-c7mq-gh6q-6q7c"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-3125"
}, {
"type" : "WEB",
"url" : "https://github.com/opennextjs/opennextjs-cloudflare/pull/1147"
}, {
"type" : "WEB",
"url" : "https://github.com/opennextjs/opennextjs-cloudflare/commit/f5bd138fd3c77e02f2aa4b9c76d55681e59e98b4"
}, {
"type" : "ADVISORY",
"url" : "https://github.com/advisories/GHSA-rvpw-p7vw-wj3m"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/opennextjs/opennextjs-cloudflare"
}, {
"type" : "WEB",
"url" : "https://www.cve.org/cverecord?id=CVE-2025-6087"
}, {
"type" : "WEB",
"url" : "https://www.npmjs.com/package/@opennextjs/cloudflare/v/1.17.1"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-706", "CWE-918" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-05T00:57:07Z",
"nvd_published_at" : "2026-03-04T19:16:19Z"
}
}