{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-126850 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-126850 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-126850 is a medium-severity security feature bypass vulnerability in Google Chrome, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-126850 and fix it if it is affected.\n\nWhat it is: CVE-2026-126850 is a medium-severity security feature bypass vulnerability in Google Chrome, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-126850 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\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-126850/ (Markdown: https://insights.sbomify.com/CVE-2026-126850/index.md)","id":"CVE-2026-126850","markdown":"https://insights.sbomify.com/CVE-2026-126850/index.md","name":"CVE-2026-126850","record":{"aliases":["DEBIAN-CVE-2026-126850","ECHO-9ac0-30eb-c42e","GHSA-5vj5-52p4-xh22"],"analysis":{"component_type":"browser","exploitable_when_present":false,"fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"mobile web browser","requires_auth":"none","requires_specific_call":false,"summary":"An attacker who compromised Chrome's renderer on Android can bypass SiteIsolation to obtain sensitive information via a crafted page.","user_interaction":"required","vuln_class":"security_feature_bypass","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"Chrome","cpe":[{"name":"Google Chrome","product":"chrome","vendor":"google"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Incorrect authorization in SiteIsolation in Google Chrome on on Android prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to obtain sensitive information via a crafted HTML page. (Chromium security severity: High)","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":"Security feature bypass in Chrome","id":"CVE-2026-126850","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:chrome","products":["google:chrome"],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Use after free in Chrome","id":"CVE-2026-126851"},"nickname":null,"packages":[],"prev":{"headline":"Memory corruption in Chrome","id":"CVE-2026-126849"},"products":["Chrome"],"published":"2026-11-11","related":[{"cvss_score":9.6,"headline":"Google Chromium V8 Type Confusion","id":"CVE-2024-4947","kev_date_added":"2024-05-20","published":"2024-05-15"},{"cvss_score":9.6,"headline":"Google Chromium Visuals Use-After-Free","id":"CVE-2024-4671","kev_date_added":"2024-05-13","published":"2024-05-09"},{"cvss_score":9.6,"headline":"Google Skia Integer Overflow","id":"CVE-2023-6345","kev_date_added":"2023-11-30","published":"2023-11-29"},{"cvss_score":9.6,"headline":"Google Chrome Skia Integer Overflow","id":"CVE-2023-2136","kev_date_added":"2023-04-21","published":"2023-04-19"},{"cvss_score":9.6,"headline":"Google Chromium GPU Heap Buffer Overflow","id":"CVE-2022-4135","kev_date_added":"2022-11-28","published":"2022-11-25"},{"cvss_score":9.6,"headline":"Google Chromium Mojo Insufficient Data Validation","id":"CVE-2022-3075","kev_date_added":"2022-09-08","published":"2022-09-26"},{"cvss_score":9.6,"headline":"Google Chromium Indexed DB API Use-After-Free","id":"CVE-2021-30633","kev_date_added":"2021-11-03","published":"2021-10-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-11-12","vendors":["Google"]},"summary":"An attacker who compromised Chrome's renderer on Android can bypass SiteIsolation to obtain sensitive information via a crafted page.","url":"https://insights.sbomify.com/CVE-2026-126850/"}