Vulnerability

CVE-2026-12018

High· 8.8CVSS8.8EPSS0%

.rules3/5

Inappropriate implementation in Mojo in Google Chrome on Windows prior to 149.0.7827.115 allowed a local attacker to perform OS-level privilege escalation via a malicious file. (Chromium security severity: High)

Threat signal

88/100

Severe

Severity

high

CVSS

8.8

EPSS

Active

CVSS

v3.1via NVDOpen in FIRST calculator →

8.8/ 10HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack VectorNetworkExploitable remotely over the internet — no local access needed.
Attack ComplexityLowNo special conditions — exploit works reliably.
Privileges RequiredNoneUnauthenticated — no credentials needed.
User InteractionRequiredRequires user action (click, file open, etc).
ScopeUnchangedImpact contained to the vulnerable component.
Confidentiality ImpactHighTotal disclosure of sensitive data.
Integrity ImpactHighTotal compromise of integrity — full data modification possible.
Availability ImpactHighTotal loss of availability — full DoS possible.

EPSS

Exploit prediction · 30-day horizonFIRST.org →

0.02%

probability of exploitation in next 30 days

higher than 4% of all CVEs

Low exploitation likelihood — defer if no other signals fire.

Vendor VEX

No VEX statements published for CVE-2026-12018. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.

SSVCTrack

Total impact on non-trivial mission systems

exploitation: none
automatable: yes
impact: total
mission: support

Lifecycle

2026-06-11Published
2026-06-12Last modified1 source

References

No source-event history recorded yet. New revisions will appear here as ingestors re-fetch this CVE.