CVE-2026-16805Patch(google / chrome)

LOWCVSS 8.8 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

Patch google chrome systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

Use after free in Blink in Google Chrome prior to 150.0.7871.186 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

google CVEs Back to dashboard

0.5/ 10 priority

Sources & remediation

Vendor / third-party advisories

https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_01320465736.html

Other references

https://issues.chromium.org/issues/523292588

Weakness type (CWE)

CWE-416

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

chrome

Threat summary

Patch or workaround signal is available
4 mentions across 4 observed days
Momentum state: stable

What's happening

Patch or workaround mentioned in 3 signals
Technical details provided in 3 signals
Disclosure: 1 classified signal
Peaked 3d ago at 1 mentions (2026-07-23); latest day: 1
4 total mentions across 4 days

Affected systems

Vendors

google

Products

chrome

Deep dive

Activity timeline4 mentions / 4d

Signal classification2 categories

Patch

375.0%

Disclosure

125.0%

Referenced assets3 URLs

By indicator

Classification over time

Date	Total	Labels

2026-07-23	1	Disclosure1
2026-07-24	1	Patch1
2026-07-25	1	Patch1
2026-08-03	1	Patch1

Full discourse4 posts

iototsecnews@iototsecnews81d
Patch
Google Chrome 150 のアップデート：Codecs／WebMCP／Blink などに影響する 4 件の脆弱性を修正 https://iototsecnews.jp/2026/07/24/google-chrome-150-update-fixes-four-high-severity-security-vulnerabilities/ 今回の Chrome のアップデートでは、主にメモリ管理に関する重大な問題が修正されました。原因の中心となっているのは、境界外書き込みの脆弱性 CVE-2026-16807 と、解放済みメモリ使用 (Use-After-Free) の脆弱性 CVE-2026-16806／CVE-2026-16805／CVE-2026-16804 です。前者はプログラムが割り当てられた領域を超えてデータを書き込んでしまうバグであり、後者は解放済みのメモリ領域へ誤ってアクセスし続けてしまうバグです。これらにより、ブラウザの不安定化や、悪意の Web コンテンツを介した不正なコード実行につながる恐れがあります。ご利用のチームは、ご注意ください。 #Chrome #CVE202616804 #CVE202616805 #CVE202616806 #CVE202616807 #Google #Vulnerability
Post summary
Google Chrome 150 update addresses four high‑severity CVEs involving memory safety bugs; the update serves as the remediation patch. No PoC, exploit, or active exploitation is reported.
00000190
504 followersView on X
Windows Forum@windowsforum90d
Patch
🔒 Chrome users: update now. A crafted webpage can exploit Blink’s use-after-free flaw to run code in the sandbox—because “just visiting a site” is still a security strategy. https://windowsforum.com/threads/cve-2026-16805-update-chrome-to-fix-high-severity-blink-flaw.440350/?utm_source=x&utm_medium=social&utm_campaign=news_node84 #WindowsSecurity #BrowserUpdates #GoogleChrome #Cve202616805 https://t.co/NH8HARdmSG
Post summary
The post warns that CVE‑2026‑16805 is a high‑severity use‑after‑free bug in Chrome’s Blink engine and urges users to update to the latest version, but it does not mention any active exploitation, PoC, or exploit code.
0000073
1.3K followersView on X
TECHEPAGES@techepages91d
Patch
🚨 Google issues emergency Chrome update fixing 4 high-severity vulnerabilities — all memory safety bugs, no confirmed active exploitation yet. Update to 150.0.7871.186/.187 (Win/macOS) or 150.0.7871.186 (Linux) now: CVE-2026-16807 – Out-of-bounds write in media codecs CVE-2026-16806 – Use-after-free in WebMCP CVE-2026-16805 – Use-after-free in Blink rendering engine CVE-2026-16804 – Use-after-free in input handling
Post summary
Google released an emergency Chrome update (v150.0.7871.186/.187) that patches four memory-safety vulnerabilities (CVE‑2026‑16807 to CVE‑2026‑16804), with no evidence of active exploitation.
0000048
32 followersView on X
VulDB 🛡@vuldb91d
Disclosure
A severe vulnerability was disclosed for Google Chrome (CVE-2026-16805) https://vuldb.com/vuln/382828
Post summary
A severe vulnerability affecting Google Chrome (CVE-2026-16805) has been disclosed, but the text offers no additional details regarding PoC, exploitation, patches, or technical specifics.
00000107
2.3K followersView on X

CPE platform detail1 entries

Part:

Vendor:

Product:

Version:

Target SW:

Target HW:

1 of 1 entries

Part	Vendor	Product	Version	Target SW	Target HW
App	google	chrome	-	-	-

Explore more

Back to dashboard google CVEs chrome vulnerabilities

What researchers are saying

CVE-2026-16805

Windows Forum[verified]@windowsforumPatch

The post warns that CVE‑2026‑16805 is a high‑severity use‑after‑free bug in Chrome’s Blink engine and urges users to update to the latest version, but it does not mention any active exploitation, PoC, or exploit code.

TECHEPAGES[verified]@techepagesPatch

Google released an emergency Chrome update (v150.0.7871.186/.187) that patches four memory-safety vulnerabilities (CVE‑2026‑16807 to CVE‑2026‑16804), with no evidence of active exploitation.

iototsecnews@iototsecnewsPatch

Google Chrome 150 update addresses four high‑severity CVEs involving memory safety bugs; the update serves as the remediation patch. No PoC, exploit, or active exploitation is reported.

VulDB 🛡@vuldbDisclosure

A severe vulnerability affecting Google Chrome (CVE-2026-16805) has been disclosed, but the text offers no additional details regarding PoC, exploitation, patches, or technical specifics.