{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-63175 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-63175 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-63175 is a high-severity vulnerability in Lookyloo PlaywrightCapture, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-63175 and fix it if it is affected.\n\nWhat it is: CVE-2026-63175 is a high-severity vulnerability in Lookyloo PlaywrightCapture, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-63175 in the wild and no public exploit code.\n\nAffected product: Lookyloo PlaywrightCapture. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-63175/ (Markdown: https://insights.sbomify.com/CVE-2026-63175/index.md)","id":"CVE-2026-63175","markdown":"https://insights.sbomify.com/CVE-2026-63175/index.md","name":"CVE-2026-63175","record":{"aliases":["GHSA-45hp-h3fx-8mr2"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python capture library","requires_auth":"low_privilege","summary":"Attackers can access other users' sensitive data and credentials due to shared mutable state in concurrent capture operations.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"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.\n\nIn 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.\n\nThe 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-Capture Session Data Leakage Due to Shared Mutable State in Looklyloo - PlaywrightCapture","id":"CVE-2026-63175","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Malcolm Vulnerable to Authorization Bypass via URI Normalization Differential in Nginx Lua RBAC","id":"CVE-2026-63177"},"packages":[],"prev":{"headline":"Omnispace Agora Project \u003c 26.10.0 Broken Access Control via spaceAffectList","id":"CVE-2026-63174"},"products":["PlaywrightCapture"],"published":"2026-07-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-16","vendors":["Lookyloo"]},"summary":"Attackers can access other users' sensitive data and credentials due to shared mutable state in concurrent capture operations.","url":"https://insights.sbomify.com/CVE-2026-63175/"}