VulnSocial

CVE-2026-16806Patch(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 WebMCP 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 CVEsBack to dashboard
0.5/ 10 priority

Sources & remediation

Vendor / third-party advisories
Other references
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
00111Mentions · 2026-07-23: 1Mentions · 2026-07-24: 1Mentions · 2026-07-25: 1Mentions · 2026-08-03: 1Patch / Workaround · 2026-07-24: 1Patch / Workaround · 2026-07-25: 1Patch / Workaround · 2026-08-03: 1Technical Details · 2026-07-24: 1Technical Details · 2026-07-25: 1Technical Details · 2026-08-03: 107-2307-2407-2508-03
Signal classification2 categories
Patch
375.0%
Disclosure
125.0%
Referenced assets3 URLs
Classification over time
DateTotalLabels
2026-07-231
Disclosure1
2026-07-241
Patch1
2026-07-251
Patch1
2026-08-031
Patch1
Full discourse4 posts
  • Windows Forum@windowsforum
    Patch

    🚨 Chrome’s shiny new WebMCP feature just got a memory-safety reality check. Update to 150.0.7871.186/.187—because “load this page” shouldn’t mean “run my code.” https://windowsforum.com/threads/cve-2026-16806-chrome-webmcp-flaw-fixed-in-150-0-7871-186.440351/?utm_source=x&utm_medium=social&utm_campaign=news_node84 #ChromeSecurity #GoogleChrome #Cve202616806 #Webmcp https://t.co/njik6n4ekm

    Post summary

    Chrome’s WebMCP flaw CVE‑2026‑16806 has been patched in version 150.0.7871.186/.187, so users should update to avoid the memory‑safety issue.

    0001072
    1.3K followersView on X
  • iototsecnews@iototsecnews
    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 release fixes four high‑severity memory‑management CVEs, including an out‑of‑bounds write and several use‑after‑free bugs, but provides no evidence of active exploitation or a PoC.

    00000190
    504 followersView on X
  • TECHEPAGES@techepages
    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 patching four high‑severity memory safety bugs; no active exploitation reports or PoC were disclosed.

    0000048
    32 followersView on X
  • VulDB 🛡@vuldb
    Disclosure

    The severity is increased for this new vulnerability affecting Google Chrome (CVE-2026-16806) https://vuldb.com/vuln/382829

    Post summary

    The post reports an increased severity for a new Google Chrome vulnerability (CVE‑2026‑16806) but provides no technical details or actionable information.

    00000119
    2.3K followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appgooglechrome---

Explore more

Back to dashboardgoogle CVEschrome vulnerabilities