How severe is GHSA-6fg3-hvw7-2fwq?

No CVSS score has been assigned to GHSA-6fg3-hvw7-2fwq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6fg3-hvw7-2fwq?

GHSA-6fg3-hvw7-2fwq affects the following packages: @playwright/mcp (npm). Ecosystems affected: npm.

How do I fix GHSA-6fg3-hvw7-2fwq?

Update @playwright/mcp to 0.0.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6fg3-hvw7-2fwq is resolved across your whole dependency graph.

How do I detect GHSA-6fg3-hvw7-2fwq in my npm dependencies?

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

How do I mitigate GHSA-6fg3-hvw7-2fwq if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-6fg3-hvw7-2fwq actively exploited in the wild?

No public exploit code has been indexed for GHSA-6fg3-hvw7-2fwq 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-6fg3-hvw7-2fwq?

GHSA-6fg3-hvw7-2fwq has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 69th 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-6fg3-hvw7-2fwq?

GHSA-6fg3-hvw7-2fwq is classified as CWE-749 (CWE-749). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6fg3-hvw7-2fwq published, and has it been updated?

GHSA-6fg3-hvw7-2fwq was published on January 7, 2026 and was last updated on February 3, 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

Microsoft Playwright MCP Server vulnerable to DNS Rebinding Attack; Allows Attackers Access to All Server ToolsGHSA-6fg3-hvw7-2fwq

Fix: microsoft/playwright@1313fbd

GHSA-6fg3-hvw7-2fwq is a CWE-749 vulnerability in @playwright/mcp. A fix is available for @playwright/mcp — see the affected versions and patch details below.

Also known asCVE-2025-9611 GHSA-8rgw-6xp9-2fg3

Published

Jan 7, 2026

Updated

Feb 3, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6fg3-hvw7-2fwq.

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% 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.

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

@playwright/mcpnpm

10.6Mdownloads / week

Description

Microsoft Playwright MCP Server versions prior to 0.0.40 fails to validate the Origin header on incoming connections. This allows an attacker to perform a DNS rebinding attack via a victim’s web browser and send unauthorized requests to a locally running MCP server, resulting in unintended invocation of MCP tool endpoints.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@playwright/mcp`	all versions	0.0.40`npm install @playwright/mcp@0.0.40`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @playwright/mcp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @playwright/mcp to 0.0.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6fg3-hvw7-2fwq is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-6fg3-hvw7-2fwq in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works