CVE-2026-12018
HIGHCVSS 8.8/10EPSS 0.16%
Last modified
CVE-2026-12018 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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). EPSS estimates a 0.16% chance of exploitation in the next 30 days.
Description
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)
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | < 149.0.7827.115 |
References
- https://issues.chromium.org/issues/516808201Issue Tracking, Permissions Required
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-12018?
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)
How severe is CVE-2026-12018?
CVE-2026-12018 has a CVSS score of 8.8/10 (HIGH severity). The EPSS model estimates a 0.16% probability of exploitation in the next 30 days.
How do I fix CVE-2026-12018?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-12012Use after free in Network in Google Chrome prior to 149.0.78…8.1
- CVE-2026-12013Rejected reason: Determined not a vulnerability
- CVE-2026-12014Use after free in Cast in Google Chrome prior to 149.0.7827.…8.3
- CVE-2026-12015Use after free in Autofill in Google Chrome prior to 149.0.7…5.3
- CVE-2026-12016Inappropriate implementation in DevTools in Google Chrome pr…8.3
- CVE-2026-12017Inappropriate implementation in Extensions in Google Chrome …3.1
- CVE-2026-12019Heap buffer overflow in Codecs in Google Chrome on Linux and…8.3
- CVE-2026-1202A security flaw has been discovered in CRMEB up to 5.6.3. Th…9.8
- CVE-2026-12020Use after free in Autofill in Google Chrome on Mac prior to …8.8
- CVE-2026-12022Race in Safe Browsing in Google Chrome on Mac prior to 149.0…8.3
- CVE-2026-12023Use after free in GPU in Google Chrome on Mac prior to 149.0…8.3
- CVE-2026-12024Insufficient policy enforcement in DevTools in Google Chrome…6.5
Are you affected by CVE-2026-12018?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST