Skip to content
Sign in Sign up
JA EN FR
SecPulse
A detailed explainer is available in Japanese. Read the Japanese explainer
Exploited High 8.8

Vulnerability in Google Chrome

CVE-2026-85046 First seen on SecPulse

AI summary

Written by an external AI model and may contain mistakes. Check the original description and references below before acting on it.

A vulnerability tracked as CVE-2026-85046 has been found in Google Chrome.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
Note: CISA has officially confirmed this is actively exploited in the wild. Treat it with elevated urgency.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Google Chrome CVE-2026-85046" on the vendor's site.

CVE-2026-85046 (Google Chrome) — CWE-843 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Listed in CISA KEV — actively exploited, treat as top priority.
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.

What is the problem

A vulnerability (CWE-843) exists in Google Chrome.

Affected scope

Check the vendor advisory for the affected versions of Google Chrome.

Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover. Listed in CISA KEV — actively exploited in the wild, treat as top priority.

How to fix

Update to the patched release per vendor advisory.

Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

Detection

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

  1. 1
    Identify exposureidentify
    grep -r 'Chrome' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Chrome を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Consider incident declarationescalate
    Notify SOC / on-call

    CISA KEV登録済 = 実環境で悪用が観測されている。侵入の兆候があればインシデント対応宣言、無くてもパッチ適用までWAF強化を最優先で。

  3. 3
    Post-deployment verificationverify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

Original description The description as published by the source.

Type confusion in V8 in Google Chrome prior to 152.0.7977.82 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

Source: Google Chrome Releases NVD GitHub Advisory CISA KEV

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details