Vulnerability in Google Chrome (CVE-2026-5289)
Summary
Vulnerability in Google Chrome (CVE-2026-5289). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A new LTS-144 version 144.0.7559.252 (Platform Version: 16503.84.0), is being rolled out for most ChromeOS devices. This version includes selected security fixes including:495931147 High CVE-2026-5289: Use after free in Navigation.497846428 High CVE-2026-6309: Use after free in Viz.487117772 High CVE-2026-4449: Use after free in Blink.488188166 High CVE-2026-4674: Out of bounds read in CSS.497412658 High CVE-2026-6308: Out of bounds read in Media.482828615 High CVE-2026-3916: Out of bounds read in Web Speech.484751092 High CVE-2026-4442: Heap buffer overflow in CSS.489619753 High CVE-2026-4458: Use after free in Extensions.487768779 High CVE-2026-4451 Insufficient validation of untrusted input in Navigation.492213293 Medium CVE-2026-5292: Out of bounds read in WebCodecs.491655161 Medium CVE-2026-5282: Out of bounds read in WebCodecs.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-5289 has been found in Google Chrome.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Google Chrome CVE-2026-5289" on the vendor's site.
CVE-2026-5289 (Google Chrome)
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.
A vulnerability (unclassified) exists in Google Chrome.
Check the vendor advisory for the affected versions of Google Chrome.
Severity: ?. Risk of unauthorized operations or information disclosure.
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-5289 chromium