Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-63175Published 2026-07-15

CVE-2026-63175 — Lookyloo PlaywrightCapture

high (derived)

As of 2026-07-16, CVE-2026-63175 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in Lookyloo PlaywrightCapture, CVSS v4.0 7.1, EPSS 0.2% (21.4th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-63175 as of 2026-07-16; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v4.0
7.1/10High (derived)
EPSS
0.2%Higher than 21.4% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
4.4/10Threadlinqs triage score
Published
Updated 2026-07-16
CVSS v4.0 7.1 (High, derived from score) · EPSS 0.2% (higher than 21.4% of all scored CVEs) · Priority 4.4/10 · Published 2026-07-15

Last updated:

What is CVE-2026-63175?

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.

The record classifies CVE-2026-63175 under weakness class CWE-613. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 82 days ago.

Severity and exploitation probability

CVSS v4.0 base score
7.1 — High (derived from score)
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N
EPSS (FIRST)
0.2% probability of exploitation in the next 30 days, higher than 21.4% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
4.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-07-15, last modified 2026-07-16

Is CVE-2026-63175 being exploited?

It currently carries a trending score of 35 in the Threadlinqs vulnerability feed.

Affected products and versions

  • Lookyloo: PlaywrightCapture

How to fix CVE-2026-63175

No vendor patch reference has been recorded for CVE-2026-63175 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-63175

No threat campaign in the Threadlinqs corpus currently references CVE-2026-63175, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, GitHub Security Advisories, FIRST EPSS. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch