CVE-2026-63175

Received Received - Intake

State Sharing in PlaywrightCapture Leading to Information Disclosure

Publication date: 2026-07-15

Last updated on: 2026-07-16

Assigner: 5a6e4751-2f3f-4070-9419-94fb35b644e8

Description

PlaywrightCapture stored capture-specific configuration and runtime data as mutable class-level variables rather than instance-level variables. Consequently, multiple Capture objects running within the same Python process could share state, including HTTP headers, cookies, browser storage, HTTP credentials, proxy configuration, user-agent settings, geolocation information, and captured request data. In a multi-user or concurrent deployment, information supplied during one capture could therefore persist and be reused by a subsequent or parallel capture. This could result in the disclosure of authentication cookies, credentials, browser storage, or captured request data belonging to another user. It could also cause requests to be performed with another capture's authentication context, headers, or proxy configuration, potentially enabling unauthorized access to remote resources or interference with other capture operations. The vulnerability is resolved by initializing all capture-specific settings and request data as instance variables in the Capture constructor, ensuring that state is isolated between capture operations.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-15

Last Modified

2026-07-16

Generated

2026-08-05

AI Q&A

2026-07-16

EPSS Evaluated

2026-08-03

NVD

CVE-2026-63175

EUVD

EUVD-2026-44823

Affected Vendors & Products

Vendor	Product	Version / Range
lookyloo	playwrightcapture	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-613	According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."

Attack-Flow Graph

Executive Summary

PlaywrightCapture stored configuration and runtime data as class-level variables instead of instance-level variables. This caused multiple Capture objects in the same Python process to share state, including sensitive data like HTTP headers, cookies, and authentication credentials. As a result, one capture could unintentionally expose or reuse data from another capture, leading to potential information disclosure or unauthorized access.

Detection Guidance

To detect this vulnerability, inspect Python applications using PlaywrightCapture for mutable class-level variables storing capture-specific data. Check for shared state between Capture objects by reviewing code for instance variables in the constructor. Look for persistent HTTP headers, cookies, or authentication data across multiple captures.

Impact Analysis

In a multi-user or concurrent environment, this vulnerability could allow an attacker to access another user's authentication cookies, credentials, or captured request data. It might also cause requests to be made with another user's authentication context, headers, or proxy settings, potentially enabling unauthorized access to remote resources or disrupting other capture operations.

Compliance Impact

This vulnerability could violate data protection regulations like GDPR or HIPAA by enabling unauthorized access to or leakage of personal or sensitive data. For instance, exposure of authentication cookies or browser storage could lead to breaches of confidentiality, resulting in non-compliance with data protection requirements.

Mitigation Strategies

Update PlaywrightCapture to the patched version where capture-specific settings are initialized as instance variables in the Capture constructor to ensure state isolation between captures.

Hi! I’m here to help you understand CVE-2026-63175. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70