Heap buffer overflow in GPU in Google Chrome prior to 107.0.5304.121 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
CVE-2022-4135
Score elevated to 9.6 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-11-28), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.6 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.6
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 9.6(high)
- EG Risk
- 83(Attend)EG Risk 83/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity96% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 32%
- EPSS %ILE
- 98%
- KEV
- ⚠ Exploited
Published
November 25, 2022
Last Modified
October 24, 2025
Advisory Details (4)
Auto-updated Sep 7, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-4135Chromium, Google Chrome, Microsoft Edge: Multiple Vulnerabilities (GLSA 202305-10) — Gentoo security
https://security.gentoo.org/glsa/202305-10Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2022/11/stable-channel-update-for-desktop_24.htmlAffected Packages
(5 across 5 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (68 versions) | 107.0.5304.121-1~deb11u1 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | — | 107.0.5304.121-1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | — | 107.0.5304.121-1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | — | 107.0.5304.121-1 | — |
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| electron | — | 19.1.8 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 53× in last 7d / 223× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 727 total refreshes for this CVE.
- 2026-09-08 07:34 UTCVendor advisory
- 2026-09-08 03:21 UTCVendor advisory
- 2026-09-07 23:07 UTCVendor advisory
- 2026-09-07 18:52 UTCEG score recompute
- 2026-09-07 18:52 UTCVendor advisory
- 2026-09-07 15:59 UTCEPSS rescore
- 2026-09-07 14:39 UTCVendor advisory
- 2026-09-07 10:23 UTCVendor advisory
- 2026-09-07 06:08 UTCVendor advisory
- 2026-09-07 01:55 UTCVendor advisory
- 2026-09-06 21:40 UTCVendor advisory
- 2026-09-06 17:27 UTCEG score recompute
- 2026-09-06 17:27 UTCVendor advisory
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-06 13:13 UTCVendor advisory
- 2026-09-06 09:00 UTCVendor advisory
- 2026-09-06 04:47 UTCVendor advisory
- 2026-09-06 00:34 UTCVendor advisory
- 2026-09-05 20:21 UTCVendor advisory
- 2026-09-05 16:07 UTCEG score recompute
- 2026-09-05 16:07 UTCVendor advisory
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-09-05 11:54 UTCVendor advisory
- 2026-09-05 07:41 UTCVendor advisory
- 2026-09-05 03:28 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-04 23:15 UTCVendor advisory
- 2026-09-04 19:01 UTCVendor advisory
- 2026-09-04 17:38 UTCCISA KEV update
- 2026-09-04 14:47 UTCEG score recompute
- 2026-09-04 14:47 UTCVendor advisory
- 2026-09-04 13:57 UTCEPSS rescore
- 2026-09-04 10:31 UTCVendor advisory
- 2026-09-04 06:17 UTCVendor advisory
- 2026-09-04 02:03 UTCVendor advisory
- 2026-09-03 21:49 UTCVendor advisory
- 2026-09-03 17:35 UTCVendor advisory
- 2026-09-03 13:19 UTCVendor advisory
- 2026-09-03 09:06 UTCVendor advisory
- 2026-09-03 04:51 UTCVendor advisory
- 2026-09-03 00:37 UTCVendor advisory
- 2026-09-02 20:22 UTCVendor advisory
- 2026-09-02 17:33 UTCCISA KEV update
- 2026-09-02 16:08 UTCEG score recompute
- 2026-09-02 16:08 UTCVendor advisory
- 2026-09-02 14:09 UTCEPSS rescore
- 2026-09-02 11:54 UTCVendor advisory
- 2026-09-02 07:37 UTCVendor advisory
- 2026-09-02 03:22 UTCVendor advisory
- 2026-09-01 23:05 UTCVendor advisory
- 2026-09-01 18:51 UTCVendor advisory
- 2026-09-01 14:36 UTCEG score recompute
- 2026-09-01 14:36 UTCVendor advisory
- 2026-09-01 13:51 UTCEPSS rescore
- 2026-09-01 10:22 UTCVendor advisory
- 2026-09-01 06:07 UTCEG score recompute
- 2026-09-01 06:07 UTCVendor advisory
- 2026-09-01 01:52 UTCVendor advisory
- 2026-08-31 21:39 UTCVendor advisory
- 2026-08-31 17:26 UTCVendor advisory
- 2026-08-31 14:19 UTCCISA KEV update
- 2026-08-31 13:12 UTCVendor advisory
- 2026-08-31 08:56 UTCVendor advisory
- 2026-08-31 04:41 UTCVendor advisory
- 2026-08-31 00:28 UTCVendor advisory
- 2026-08-30 20:14 UTCEG score recompute
- 2026-08-30 20:14 UTCVendor advisory
- 2026-08-30 19:15 UTCEPSS rescore
- 2026-08-30 16:01 UTCVendor advisory
- 2026-08-30 11:48 UTCVendor advisory
- 2026-08-30 07:35 UTCVendor advisory
- 2026-08-30 03:22 UTCEG score recompute
- 2026-08-30 03:22 UTCVendor advisory
- 2026-08-30 01:19 UTCEPSS rescore
- 2026-08-29 23:08 UTCVendor advisory
- 2026-08-29 18:55 UTCVendor advisory
- 2026-08-29 14:40 UTCVendor advisory
- 2026-08-29 10:27 UTCVendor advisory
- 2026-08-29 06:14 UTCVendor advisory
- 2026-08-29 02:01 UTCVendor advisory
- 2026-08-28 21:47 UTCEG score recompute
- 2026-08-28 21:47 UTCVendor advisory
- 2026-08-28 21:38 UTCEPSS rescore
- 2026-08-28 17:32 UTCVendor advisory
- 2026-08-28 13:17 UTCVendor advisory
- 2026-08-28 09:01 UTCVendor advisory
- 2026-08-28 04:44 UTCVendor advisory
- 2026-08-28 00:31 UTCVendor advisory
- 2026-08-27 20:17 UTCVendor advisory
- 2026-08-27 17:22 UTCCISA KEV update
- 2026-08-27 15:59 UTCEG score recompute
- 2026-08-27 15:59 UTCVendor advisory
- 2026-08-27 14:22 UTCEPSS rescore
- 2026-08-27 11:45 UTCVendor advisory
- 2026-08-27 07:31 UTCVendor advisory
- 2026-08-27 03:18 UTCVendor advisory
- 2026-08-26 23:04 UTCVendor advisory
- 2026-08-26 18:51 UTCEG score recompute
- 2026-08-26 18:51 UTCVendor advisory
- 2026-08-26 17:41 UTCCISA KEV update
- 2026-08-26 14:43 UTCEPSS rescore
Frequently asked(6)
What is CVE-2022-4135?
When was CVE-2022-4135 disclosed?
Is CVE-2022-4135 actively exploited?
What is the CVSS score of CVE-2022-4135?
Which products are affected by CVE-2022-4135?
How do I remediate CVE-2022-4135?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-4135
Is Your Infrastructure Affected by CVE-2022-4135?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.