Threats / Google / CVE-2022-3075
CVE-2022-3075
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Google Chromium Mojo vulnerability
Google Chromium Mojo insufficient data validation allows sandbox escape. A remote attacker with a compromised renderer process can exploit a crafted HTML page to escape the sandbox.
Verdict
Today item — known-exploited.
A renderer-process compromise combined with insufficient input validation in Mojo enables sandbox escape, potentially granting full system access. This affects Chromium-based browsers including Chrome, Edge, and Opera.
CISA KEV Yes · 2022-09-084EPSS 0.0568 (verify live)5CVSS 9.6 (CISA)3CISA SSVC Exploitation: active · Automatable: no · Impact: total3
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-09-08).
Probability (EPSS)
EPSS 0.0568 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.6 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) · Affected: Google, Chromium Mojo. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-20 Improper Input Validation.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious HTML page designed to trigger insufficient data validation in Chromium Mojo.
Business
User visits attacker-controlled or compromised website, initiating the attack chain.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit the validation flaw to escape the renderer sandbox after compromising the renderer process.
Business
Attacker gains elevated privileges beyond the sandboxed renderer, accessing system resources.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute arbitrary code with system-level permissions on the victim's machine.
Business
Complete system compromise, data theft, malware installation, or lateral movement becomes possible.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05