Use-After-Free in Google Chrome (CVE-2026-6297)
Summary
Vulnerability in Google Chrome (CVE-2026-6297). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
A new LTS-144 version 144.0.7559.249 (Platform Version: 16503.81.0), is being rolled out for most ChromeOS devices. This version includes selected security fixes including:493628982 Critical CVE-2026-6297 Use after free in Proxy.488617440 High CVE-2026-4456 Use after free in Digital Credentials API.491869946 High CVE-2026-4680 Use after free in FedCM. 488270257 High CVE-2026-4675 Heap buffer overflow in WebGL.Release notes for LTS-144 can be found here Want to know more about Long-term Support? Click hereAndy WuGoogle Chrome OS
Source: Google Chrome Releases NVD
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-6297 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-6297" on the vendor's site.
CVE-2026-6297 (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 でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-6297 chromium