Google Chromium Mojo Insufficient Data Validation Vulnerability
Insufficient data validation in Mojo in Google Chrome prior to 105.0.5195.102 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page.
Severity = CVSS. Probability = EPSS (FIRST). Exploitation = public signals: KEV, EUVD, ransomware, EPSS above 10 %, no account required.
Exploitation probability EPSS · FIRST
Exploitation signals 3 / 5
- KEV catalog (CISA)08 Sept 2022
- Exploited in EUVD (ENISA)08 Sept 2022
- Used by ransomwareno
- EPSS above 10 %5.8%
- No account, over the networkyes
What to do
Fix
Apply the vendor’s fix as soon as it is available.
CISA guidance: Apply updates per vendor instructions.
Meanwhile
Take the service off the internet or restrict access to it, watch the logs and look for signs of compromise.
Manufacturers (CRA)
Exploited vulnerability in your product: early warning to ENISA within 24 h, then notification within 72 h (Article 14 of the Cyber Resilience Act). The CRA explained
Affected products
- unspecified <105.0.5195.102
Open source packages OSV
Affected libraries according to OSV, with fixed versions.
Timeline
-
Exploitation reported (ENISA)
-
Added to the KEV catalog
-
Published
-
CISA remediation due date
References
Other exploited vulnerabilities from the same vendor
- CVE-2026-111497Google Brotli Unchecked Return Value Vulnerability8.6 · Rising fast
- CVE-2026-58704Google Pixel Improper Authorization Vulnerability4.7 · Actively exploited
- CVE-2026-87491Google Chromium V8 Out of Bounds Write Vulnerability5.4 · Actively exploited
- CVE-2026-85046Google Chromium V8 Type Confusion Vulnerability5.4 · Actively exploited
- CVE-2026-11645Google Chromium V8 Out-of-Bounds Read and Write Vulnerability5.4 · Actively exploited
- CVE-2026-5281Google Dawn Use-After-Free Vulnerability6.3 · Background exploitation