CVE-2025-6087: create-cloudflare · Server-Side Request Forgery (SSRF)
Affects create-cloudflareSource CVE Database V5
Not known to be exploited · CVSS 7.8 High : upgrade to 2.49.3 soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.49.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:H/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade create-cloudflare to 2.49.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmcreate-cloudflarepkg:npm/create-cloudflareOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Beyond upgrading to @opennextjs/cloudflare version 1.3.0 and create-cloudflare version 2.49.3, European organizations should implement the following specific mitigations: 1) Strictly configure the remotePatterns filter in Next.js to allow-list only trusted external image sources, minimizing the risk of proxying malicious content. 2) Conduct thorough audits of all web applications using the Cloudflare adapter for Open Next to identify and remediate any instances running vulnerable versions. 3) Monitor web traffic logs for unusual requests to the /_next/image endpoint, particularly those with suspicious or unexpected URL parameters, to detect potential exploitation attempts. 4) Employ Web Application Firewalls (WAF) with custom rules to block or alert on SSRF-like request patterns targeting the vulnerable endpoint. 5) Review internal network segmentation and firewall rules to ensure that even if SSRF is exploited, internal services are not accessible or are protected by additional authentication layers. 6) Educate development and security teams about SSRF risks and secure coding practices related to proxying external resources. 7) Coordinate with Cloudflare support to confirm that platform-level mitigations are active and properly configured for their deployments. These targeted actions will help reduce the attack surface and improve detection and response capabilities.
Description
A Server-Side Request Forgery (SSRF) vulnerability was identified in the @opennextjs/cloudflare package. The vulnerability stems from an unimplemented feature in the Cloudflare adapter for Open Next, which allowed unauthenticated users to proxy arbitrary remote content via the /_next/image endpoint. This issue allowed attackers to load remote resources from arbitrary hosts under the victim site’s domain for any site deployed using the Cloudflare adapter for Open Next. For example: https://victim-site.com/_next/image?url=https://attacker.com In 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. Impact: * SSRF via unrestricted remote URL loading * Arbitrary remote content loading * Potential internal service exposure or phishing risks through domain abuse Mitigation: The following mitigations have been put in place: * Server side updates to Cloudflare’s platform to restrict the content loaded via the /_next/image endpoint to images. The update automatically mitigates the issue for all existing and any future sites deployed to Cloudflare using the affected version of the Cloudflare adapter for Open Next * Root cause fix https://github.com/opennextjs/opennextjs-cloudflare/pull/727 to the Cloudflare adapter for Open Next. The patched version of the adapter is found here @opennextjs/cloudflare@1.3.0 https://www.npmjs.com/package/@opennextjs/cloudflare/v/1.3.0 * Package dependency update https://github.com/cloudflare/workers-sdk/pull/9608 to create-cloudflare (c3) to use the fixed version of the Cloudflare adapter for Open Next. The patched version of create-cloudflare is found here: create-cloudflare@2.49.3 https://www.npmjs.com/package/create-cloudflare/v/2.49.3 In addition to the automatic mitigation deployed on Cloudflare’s platform, we encourage affected users to upgrade to @opennext/cloudflare v1.3.0 and use the remotePatterns https://nextjs.org/docs/pages/api-reference/components/image#remotepatterns filter in Next config https://nextjs.org/docs/pages/api-reference/components/image#remotepatterns if they need to allow-list external urls with images assets.