LiveActive security incident?Get immediate response
CVE Record

CVE-2025-9611: Microsoft Playwright MCP Server < 0.0.40 DNS Rebinding via Missing Origin Header Validation

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.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Older Microsoft Playwright MCP Server releases could accept browser-driven requests without validating the Origin header. A malicious website could use DNS rebinding to reach a victim’s local MCP server and trigger MCP tool endpoints without authorization.

Executive priority

Treat as high priority for developer security. The likely blast radius depends on what MCP tools can do in affected environments, especially file, browser, or automation actions.

Technical view

Versions before 0.0.40 fail to validate Origin on incoming connections. With user browser interaction, DNS rebinding can target a locally running MCP server and cause unintended invocation of tool endpoints. CVSS v4.0 score is 7.2 high.

Likely exposure

Primarily developer workstations, test systems, or automation environments running Microsoft Playwright MCP Server before 0.0.40 locally while users browse attacker-controlled content.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires a victim browser and a locally running vulnerable MCP server reachable through DNS rebinding.

Researcher notes

Focus validation on local MCP server exposure and version state. Avoid assuming internet-facing exposure; the described path is browser-mediated DNS rebinding against a local service. Exploit evidence is not established in the provided sources.

Mitigation direction

  • Upgrade Microsoft Playwright MCP Server to 0.0.40 or later.
  • Review the GitHub advisory and patch commit for vendor guidance.
  • Stop local MCP server instances when not actively needed.
  • Prioritize environments where MCP tools can affect files, browsers, credentials, or automation workflows.

Validation and detection

  • Inventory Playwright MCP Server versions across developer and CI environments.
  • Confirm no running instances are below version 0.0.40.
  • Verify deployed builds include the Origin validation patch.
  • Review local MCP activity for unexpected tool endpoint invocations.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-749: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-9611 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H/SC:L/SI:L/SA:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H/SC:L/SI:L/SA:LVulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

7.2High
CVSS 4.0 vector shape for CVE-2025-9611Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:H/SC:L/SI:L/SA:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftPlaywright0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-749 · source CWE mapping

Exposed Dangerous Method or Function

Exposed Dangerous Method or Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.