Widely used Chrome browser; LPE could enable SYSTEM access on Windows, risking endpoints.
CVE-2026-12018
Chrome on Windows local privilege escalation via Mojo file
Is CVE-2026-12018 being exploited?
Not confirmed. CVE-2026-12018 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.16% probability of exploitation in the next 30 days.
How severe is CVE-2026-12018?
CVE-2026-12018 is rated High with a CVSS score of 8.8. 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-12018?
Yes. A fix has been recorded for CVE-2026-12018. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-12018 affect?
CVE-2026-12018 affects Google Chrome (Mojo) on Windows, before version 149.0.7827.115. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-12018?
Patch to latest Chrome build immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local OS-level privilege escalation via crafted file in Mojo, enabling SYSTEM on Windows
Immediate action required
- affected< 149.0.7827.115
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.