{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-130958 in the wild and no public exploit code.","exposure":"","fix":"Upgrade Google Chrome to 158.0.8127.36 or later. The advisory says that version fixes it.","what":"CVE-2026-130958 is a medium-severity vulnerability in Google Chrome, published on 17 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-130958 and fix it if it is affected.\n\nWhat it is: CVE-2026-130958 is a medium-severity vulnerability in Google Chrome, published on 17 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-130958 in the wild and no public exploit code.\n\nAffected product: Google Chrome. 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-130958/ (Markdown: https://insights.sbomify.com/CVE-2026-130958/index.md)","id":"CVE-2026-130958","markdown":"https://insights.sbomify.com/CVE-2026-130958/index.md","name":"CVE-2026-130958","record":{"aliases":["DEBIAN-CVE-2026-130958","ECHO-3178-a211-3fb7","GHSA-f6w7-93vf-fp62"],"analysis":null,"analysis_generated_by":null,"assigner":"Chrome","component":null,"cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"Uninitialized resource in WebRTC in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to read memory inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Uninitialized resource in WebRTC in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to read memory inside the sandbox via a crafted HTML page.","id":"CVE-2026-130958","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":2,"n_vendor_status":0,"next":{"headline":"Missing authorization in FileSystem in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer proce","id":"CVE-2026-130959"},"nickname":null,"packages":[],"prev":{"headline":"Improper state validation in Performance in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to potentially execute arbitrary","id":"CVE-2026-130957"},"products":["Chrome"],"published":"2026-11-17","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","text_fixes":["158.0.8127.36"],"updated":"2026-11-18","vendor_status":[],"vendors":["Google"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-130958/"}