CVE-2025-6087
Published: 16 June 2025
Summary
CVE-2025-6087 is a high-severity SSRF (CWE-918) vulnerability in Cloudflare Create-Cloudflare. Its CVSS base score is 7.8 (High).
Operationally, ranked in the top 33.6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
A Server-Side Request Forgery vulnerability tracked as CVE-2025-6087 affects the @opennextjs/cloudflare package, specifically an unimplemented feature in the Cloudflare adapter for Open Next. The flaw resides in the /_next/image endpoint, which accepted arbitrary remote URLs without restriction and allowed unauthenticated proxying of content from any host.
Unauthenticated attackers can exploit the issue by supplying attacker-controlled URLs to the endpoint on any site deployed with the vulnerable adapter, causing the victim domain to serve remote resources. This enables domain abuse that violates same-origin expectations, supports phishing or content-injection attacks, and may expose internal services reachable from the Cloudflare worker environment.
Cloudflare deployed an automatic platform-side restriction that limits the endpoint to image content for all existing and future deployments. The root-cause fix was released in @opennextjs/cloudflare 1.3.0, accompanied by an update to create-cloudflare 2.49.3; users are also advised to configure Next.js remotePatterns allow-lists after upgrading.
EPSS rose from a low baseline of 0.0050 to a peak of 0.0125, indicating emerging exploitation interest after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-18433
Vulnerability details
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…
more
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.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Penetration testing attempts server-side requests to internal resources, identifying SSRF weaknesses for remediation.
Outbound connections to external resources can be monitored and limited at the boundary, reducing SSRF impact.
Validates server-side URLs and resource references to block SSRF attempts.
Detects server-side request forgery through monitoring of unexpected outbound connections.