Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🛡️
CISA KEV · ACTIVELY EXPLOITED
CRITICAL severity

CVE-2022-3075 — Chrome

CRITICAL

CVE-2022-3075 is a critical-severity (CVSS 9.6) Improper Input Validation vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-09-08) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Published
Updated
Affected
2 products
Patched
See advisory
Exploits
3 known
Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

  • Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-09-08. Federal agencies were required to remediate by 2022-09-29.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2022-3075.

EPSS Exploitation Probability

via FIRST.org ↗
5.8%probability of exploitation in next 30 days
Lower Risk+0.04%
Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk
1.00%2.99%4.98%6.96%2.1%5.8%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2022-3075 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 395,249 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

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.

Affected Products

2 products · 2 configurations
OS
fedorafedoraproject
1 version
37
Application
chromegoogle
< 105.0.5195.102
range
Exploits & PoCs
3

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Insufficient data validation in Mojo in Google Chrome prior to 105.0.519…

chromereleases.googleblog.comChromeSep 2022

Insufficient data validation in Mojo in Google Chrome prior to 105.0.519…

cisa.govCISASep 2022

Insufficient data validation in Mojo in Google Chrome prior to 105.0.519…

chromereleases.googleblog.comGoogle-sheetAug 2022

Detection & mitigation playbook

Vulnerability

  1. Detect

    Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

  2. Remediation status

    No fixed release is recorded for CVE-2022-3075 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2022-3075 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works
Actively Exploited: CVE-2022-3075: Chrome (Critical 9.6)