How severe is GHSA-rvpw-p7vw-wj3m?

No CVSS score has been assigned to GHSA-rvpw-p7vw-wj3m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rvpw-p7vw-wj3m?

GHSA-rvpw-p7vw-wj3m affects the following packages: @opennextjs/cloudflare (npm). Ecosystems affected: npm.

How do I fix GHSA-rvpw-p7vw-wj3m?

Update @opennextjs/cloudflare to 1.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rvpw-p7vw-wj3m is resolved across your whole dependency graph.

How do I detect GHSA-rvpw-p7vw-wj3m in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @opennextjs/cloudflare, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rvpw-p7vw-wj3m if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-rvpw-p7vw-wj3m actively exploited in the wild?

No public exploit code has been indexed for GHSA-rvpw-p7vw-wj3m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-rvpw-p7vw-wj3m?

GHSA-rvpw-p7vw-wj3m has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-rvpw-p7vw-wj3m?

GHSA-rvpw-p7vw-wj3m is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-rvpw-p7vw-wj3m published, and has it been updated?

GHSA-rvpw-p7vw-wj3m was published on June 16, 2025 and was last updated on March 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

OpenNext for Cloudflare (opennextjs-cloudflare) has a SSRF vulnerability via /_next/image endpointGHSA-rvpw-p7vw-wj3m

Fix: cloudflare/workers-sdk#9608

GHSA-rvpw-p7vw-wj3m is a Server-Side Request Forgery (SSRF) vulnerability in @opennextjs/cloudflare. A fix is available for @opennextjs/cloudflare — see the affected versions and patch details below.

Also known asCVE-2025-6087 CVE-2026-3125 GHSA-c7mq-gh6q-6q7c

Published

Jun 16, 2025

Updated

Mar 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rvpw-p7vw-wj3m.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

11other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@opennextjs/cloudflarenpm

2.3Mdownloads / week

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: Pull request 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/[email protected]

Package dependency update: Pull request 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 at [email protected].

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 filter in Next config if they need to allow-list external urls with images assets.

Credits

Disclosed responsibly by security researcher Edward Coristine. Thank you for the report.

References

https://www.cve.org/cverecord?id=CVE-2025-6087

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@opennextjs/cloudflare`	all versions	1.3.0`npm install @opennextjs/cloudflare@1.3.0`

Affected Products

2 products · 2 configurations

Application

create-cloudflarecloudflare

< 2.49.3

range

Application

opennext for cloudflareopennextjs

< 1.3.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @opennextjs/cloudflare, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @opennextjs/cloudflare to 1.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rvpw-p7vw-wj3m is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

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 conten

O3 Security · Impact-Aware SCA

Is GHSA-rvpw-p7vw-wj3m in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works