Quick answers
- Is CVE-2026-63175 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63175 being exploited in the wild.
- How severe is CVE-2026-63175?
- Informational severity, with a CVSS score of 7.1, published 15 July 2026.
- Which products and versions are affected?
- Lookyloo PlaywrightCapture <= v1.40.2.
- Is there a fix for CVE-2026-63175?
- A patch was published on 2026-07-15: Fix committed to repository Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63175 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-63175?
- Check whether you run Lookyloo PlaywrightCapture at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability arises from the use of mutable class-level variables (such as _headers, _cookies, and _requests) instead of instance-level variables within the Capture class. In multi-user or concurrent Python deployments, multiple Capture objects share the same memory space for these variables, leading to state pollution. An attacker or a concurrent process could inadvertently access or reuse authentication headers, cookies, proxy configurations, and captured request data belonging to a different session. The issue is resolved by moving these variables into the __init__ constructor to ensure proper instance isolation.
Affected products
- Lookyloo PlaywrightCapture <= v1.40.2
Timeline
- 2026-07-15: advisory: NVD publication date
- 2026-07-15: patched: Fix committed to repository