CVE-2022-3075

Exp

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.

Published: 2022-09-26 Last update: 2025-10-24 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-3075 is rated Critical Active Threat (91.9/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 2.12%). CISA KEV confirms active exploitation (added 2022-09-08) affecting Google / Chromium Mojo. a weakness (CWE-20) Unauthenticated remote administrative access may be possible. The CISA remediation deadline has passed—treat as an emergency patch priority.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

CISA KEV Record for CVE-2022-3075

Name: Google Chromium Mojo Insufficient Data Validation Vulnerability · CISA KEV detail

Exploit added: 2022-09-08

Action due: 2022-09-29

Required action: Apply updates per vendor instructions.

Exploit prediction scoring system (EPSS) score for CVE-2022-3075

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-20 2.99% 2.12% -0.87%
2 2025-12-24 2.12% 2.99% +0.87%
3 2025-11-25 — 2.12% —

Full EPSS history (31 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-3075

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.6 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 6.0 [email protected]
9.6 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 6.0 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2022-3075

OS Trackers for CVE-2022-3075

vendor priority summary link
alpine — CVE-2022-3075: 1 source package rows (qt5-qtwebengine); 7 state rows across 7 repos (3.17-community, 3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 7, open 0. https://security.alpinelinux.org/vuln/CVE-2022-3075
debian not yet assigned CVE-2022-3075 not yet assigned priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-3075
gentoo high CVE-2022-3075: 1 GLSA(s) (202209-23), 4 atom(s) (www-client/chromium, www-client/chromium-bin, www-client/google-chrome, www-client/microsoft-edge); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-3075
ubuntu medium CVE-2022-3075 medium priority: Ubuntu including 1 source packages (chromium-browser), 7 status rows across 7 suites (bionic, focal, jammy, kinetic, trusty, upstream, xenial): ignored 2, not-affected 2, released 2, DNE 1. https://ubuntu.com/security/CVE-2022-3075

Affected software / configurations for CVE-2022-3075

Vendor Product Version Raw CPE
google chrome < 105.0.5195.102 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
fedoraproject fedora 37 cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*

References for CVE-2022-3075

cvelogic Threat Intelligence