Affects Google Chrome; widely-used browser; high risk of remote code execution via crafted HTML (heap corruption).
CVE-2026-3918
Use-after-free in Chrome WebMCP allows remote heap corruption via crafted HTML page.
Is CVE-2026-3918 being exploited?
Not confirmed. CVE-2026-3918 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-3918?
CVE-2026-3918 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-3918?
Yes. A fix has been recorded for CVE-2026-3918. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-3918 affect?
CVE-2026-3918 affects Google Chrome. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-3918?
Update to 146.0.7680.71 or later.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can trigger heap corruption via crafted HTML page, potentially enabling remote code execution in Chrome.
Patch when possible
- affected< 146.0.7680.71
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.