Use-After-Free in Google Chrome (CVE-2026-19137)
Summary
Vulnerability in Google Chrome (CVE-2026-19137). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
Use after free in WebGL in Google Chrome on Android prior to 151.0.7922.109 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
Source: Google Chrome Releases NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-19137 has been found in Google Chrome.
Successful exploitation can lead to full system takeover. CVSS score: 8.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Google Chrome CVE-2026-19137" on the vendor's site.
CVE-2026-19137 (Google Chrome) — CWE-416 / CVSS v3 8.3
Attack vector: remote (network-reachable) / unauthenticated
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Use-after-free (CWE-416) exists in Google Chrome.
Check the vendor advisory for the affected versions of Google Chrome.
Severity: High (CVSS 8.3/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Chrome' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Chrome' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Chromeを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- CHROME chromereleases.googleblog.com
- patch chrome-cve-admin@google.com
- web chrome-cve-admin@google.com
- web nvd.nist.gov
- web github.com