Impact
A Server‑Side Request Forgery flaw exists in the @opennextjs/cloudflare adapter for Cloudflare Workers. By replacing the forward slash in the /cdn‑cgi/image/ path with a backslash, the Cloudflare edge layer bypasses its request filtering and the backslash is normalized by JavaScript’s URL class, enabling an attacker to trigger an unvalidated fetch of any remote URL. The retrieved content is then served through the victim’s domain, breaking the same‑origin policy and potentially allowing malicious payloads or sensitive data to be displayed or further accessed by downstream services. The same bypass also exposes previously protected assets under /cdn‑cgi/ paths, such as the cached data stored under /cdn‑cgi/_next_cache in Open Next projects.
Affected Systems
Installed versions of the @opennextjs/cloudflare Node.js package are vulnerable; it is inferred that any deployment using a version older than the patched release 1.17.1 is affected. The flaw also impacts Cloudflare Workers, Pages, and Assets environments that expose /cdn‑cgi/ paths, including the cache stored under /cdn‑cgi/_next_cache in Open Next projects.
Risk and Exploitability
The flaw carries a CVSS v3.1 score of 7.7, marking it as high severity. The EPSS probability is less than 1%, indicating a low likelihood of exploitation. The vulnerability is not listed in CISA’s KEV catalog. Attackers can exploit the bypass using HTTP clients that preserve backslashes, such as curl with the --path-as-is option; this limits the vector to non-browser clients but still permits automated or scripted attacks that could exfiltrate data or serve malicious content through the victim’s domain.
OpenCVE Enrichment
Github GHSA