How severe is GHSA-fwvg-2739-22v7?

GHSA-fwvg-2739-22v7 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-fwvg-2739-22v7?

GHSA-fwvg-2739-22v7 affects the following packages: miniflare (npm). Ecosystems affected: npm.

How do I fix GHSA-fwvg-2739-22v7?

Update miniflare to 3.20231030.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fwvg-2739-22v7 is resolved across your whole dependency graph.

How do I detect GHSA-fwvg-2739-22v7 in my npm dependencies?

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

How do I mitigate GHSA-fwvg-2739-22v7 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-fwvg-2739-22v7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-fwvg-2739-22v7 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-fwvg-2739-22v7?

GHSA-fwvg-2739-22v7 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 46th 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-fwvg-2739-22v7?

GHSA-fwvg-2739-22v7 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-fwvg-2739-22v7 published, and has it been updated?

GHSA-fwvg-2739-22v7 was published on December 29, 2023 and was last updated on July 8, 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

HIGH severity

Miniflare vulnerable to Server-Side Request Forgery (SSRF)GHSA-fwvg-2739-22v7

HIGHFix: cloudflare/workers-sdk#4532

GHSA-fwvg-2739-22v7 is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in miniflare. A fix is available for miniflare — see the affected versions and patch details below.

Also known asCVE-2023-7078

Published

Dec 29, 2023

Updated

Jul 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-fwvg-2739-22v7.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs46th percentile — riskier than 46% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

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.

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

miniflarenpm

47.6Mdownloads / week

Description

Impact

Sending specially crafted HTTP requests to Miniflare's server could result in arbitrary HTTP and WebSocket requests being sent from the server. If Miniflare was configured to listen on external network interfaces (as was the default in wrangler until 3.19.0), an attacker on the local network could access other local servers.

Patches

The issue was fixed in [email protected].

Workarounds

Ensure Miniflare is configured to listen on just local interfaces. This is the default behaviour, but can also be configured with the host: "127.0.0.1" option.

References

https://github.com/cloudflare/workers-sdk/pull/4532

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`miniflare`	≥ 3.20230821.0&&< 3.20231030.2	3.20231030.2`npm install miniflare@3.20231030.2`

Affected Products

1 product · 1 configurations

Application

miniflarecloudflare

≥ 3.20230821.0 && < 3.20231030.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for miniflare, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update miniflare to 3.20231030.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fwvg-2739-22v7 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

### Impact Sending specially crafted HTTP requests to Miniflare's server could result in arbitrary HTTP and WebSocket requests being sent from the server. If Miniflare was configured to listen on external network interfaces (as was the default in `wrangler` until `3.19.0`), an attacker on the local network could access other local servers. ### Patches The issue was fixed in `[email protected]`. ### Workarounds Ensure Miniflare is configured to listen on just local interfaces. This is the default behaviour, but can also be configured with the `host: "127.0.0.1"` option. ### References -