CVE-2026-63175 Details
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.
A vulnerability in PlaywrightCapture allows for the unintentional sharing of state between Capture objects within the same Python process. This issue arises because capture-specific configuration and runtime data are stored as mutable class-level variables instead of instance-level variables. As a result, multiple Capture objects can inadvertently share sensitive information such as HTTP headers, cookies, browser storage, HTTP credentials, proxy settings, user-agent information, geolocation data, and captured request details. In environments with multiple users or concurrent operations, this could lead to the unauthorized disclosure of authentication cookies, credentials, or other personal data, and could allow requests to be made using another user's authentication context or proxy configuration, potentially causing unauthorized access to remote resources or disrupting other capture processes.
The vulnerability has been addressed by modifying PlaywrightCapture to store all capture-specific settings and request data as instance variables in the Capture constructor, ensuring that each capture operation remains isolated. Users should update to the latest version of PlaywrightCapture to apply this fix.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Jul 15, 2026CISA-ADP
Assessed Jul 16, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/Lookyloo/PlaywrightCapture/commit/1e354b9d8566f49dbb331410be24c7c295645d43 | CIRCL | Source CodeVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-613 | Insufficient Session Expiration | CIRCL |
Affected Products
| Product | Versions |
|---|---|
| Lookyloo PlaywrightCapture | All versions |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 24, 2026 | CVE Translated | [email protected] |
| Jul 16, 2026 | CVE Modified | CISA-ADP |
| Jul 15, 2026 | New CVE Received | CIRCL |
Volerion