CVE-2022-4135

CRITICALNVD 9.69.6—
EchelonGraph scoreHIGH confidence

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.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 4 sources updated this weekExploited in the wild
9.6
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 32%CVSS: 9.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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)

CVSS v3
9.6
EG Score
9.6(high)
EPSS
98.1%
KEV
⚠ Exploited

Published

November 25, 2022

Last Modified

October 24, 2025

Advisory Details (4)

Auto-updated Jun 1, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa.
cisa Patch Available🔴 Active Exploitation

Known 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-4135
generic

Chromium, Google Chrome, Microsoft Edge: Multiple Vulnerabilities (GLSA 202305-10) — Gentoo security

https://security.gentoo.org/glsa/202305-10
generic
https://crbug.com/1392715
generic🔴 Active Exploitation

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2022/11/stable-channel-update-for-desktop_24.html

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
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 55× in last 7d / 216× 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 390 total refreshes for this CVE.

  1. 2026-07-22 04:01 UTCVendor advisory
  2. 2026-07-21 23:47 UTCVendor advisory
  3. 2026-07-21 19:19 UTCEG score recompute
  4. 2026-07-21 19:19 UTCVendor advisory
  5. 2026-07-21 15:23 UTCEPSS rescore
  6. 2026-07-21 15:23 UTCEPSS rescore
  7. 2026-07-21 15:04 UTCVendor advisory
  8. 2026-07-21 14:37 UTCCISA KEV update
  9. 2026-07-21 10:51 UTCVendor advisory
  10. 2026-07-21 06:36 UTCVendor advisory
  11. 2026-07-21 02:22 UTCVendor advisory
  12. 2026-07-20 22:08 UTCVendor advisory
  13. 2026-07-20 17:54 UTCEG score recompute
  14. 2026-07-20 17:54 UTCVendor advisory
  15. 2026-07-20 17:05 UTCEPSS rescore
  16. 2026-07-20 09:28 UTCVendor advisory
  17. 2026-07-20 05:14 UTCVendor advisory
  18. 2026-07-20 01:01 UTCVendor advisory
  19. 2026-07-19 20:48 UTCVendor advisory
  20. 2026-07-19 16:34 UTCEG score recompute
  21. 2026-07-19 16:34 UTCVendor advisory
  22. 2026-07-19 14:29 UTCEPSS rescore
  23. 2026-07-19 14:29 UTCEPSS rescore
  24. 2026-07-19 12:21 UTCVendor advisory
  25. 2026-07-19 08:08 UTCVendor advisory
Show 75 more
  1. 2026-07-19 03:54 UTCVendor advisory
  2. 2026-07-18 19:26 UTCVendor advisory
  3. 2026-07-18 15:13 UTCVendor advisory
  4. 2026-07-18 10:59 UTCEG score recompute
  5. 2026-07-18 10:59 UTCVendor advisory
  6. 2026-07-18 10:03 UTCEPSS rescore
  7. 2026-07-18 10:03 UTCEPSS rescore
  8. 2026-07-18 06:46 UTCVendor advisory
  9. 2026-07-18 02:32 UTCVendor advisory
  10. 2026-07-17 22:18 UTCVendor advisory
  11. 2026-07-17 18:05 UTCVendor advisory
  12. 2026-07-17 13:51 UTCVendor advisory
  13. 2026-07-17 09:38 UTCEG score recompute
  14. 2026-07-17 09:38 UTCVendor advisory
  15. 2026-07-17 05:24 UTCVendor advisory
  16. 2026-07-17 01:10 UTCVendor advisory
  17. 2026-07-16 20:56 UTCVendor advisory
  18. 2026-07-16 17:04 UTCCISA KEV update
  19. 2026-07-16 17:00 UTCEPSS rescore
  20. 2026-07-16 12:23 UTCVendor advisory
  21. 2026-07-16 08:07 UTCVendor advisory
  22. 2026-07-16 03:54 UTCVendor advisory
  23. 2026-07-15 23:41 UTCVendor advisory
  24. 2026-07-15 19:27 UTCVendor advisory
  25. 2026-07-15 16:56 UTCEPSS rescore
  26. 2026-07-15 16:56 UTCEPSS rescore
  27. 2026-07-15 16:49 UTCCISA KEV update
  28. 2026-07-15 15:14 UTCVendor advisory
  29. 2026-07-15 15:04 UTCCISA KEV update
  30. 2026-07-15 10:59 UTCVendor advisory
  31. 2026-07-15 06:45 UTCVendor advisory
  32. 2026-07-15 02:32 UTCVendor advisory
  33. 2026-07-15 01:58 UTCEPSS rescore
  34. 2026-07-15 01:58 UTCEPSS rescore
  35. 2026-07-14 22:17 UTCVendor advisory
  36. 2026-07-14 18:05 UTCCISA KEV update
  37. 2026-07-14 18:03 UTCVendor advisory
  38. 2026-07-14 13:50 UTCVendor advisory
  39. 2026-07-14 09:37 UTCVendor advisory
  40. 2026-07-14 05:24 UTCVendor advisory
  41. 2026-07-14 01:11 UTCVendor advisory
  42. 2026-07-13 17:07 UTCCISA KEV update
  43. 2026-07-13 06:11 UTCEPSS rescore
  44. 2026-07-13 06:11 UTCEPSS rescore
  45. 2026-07-13 04:00 UTCVendor advisory
  46. 2026-07-12 23:46 UTCVendor advisory
  47. 2026-07-12 19:33 UTCVendor advisory
  48. 2026-07-12 15:19 UTCVendor advisory
  49. 2026-07-12 11:04 UTCVendor advisory
  50. 2026-07-12 06:51 UTCVendor advisory
  51. 2026-07-12 05:44 UTCEPSS rescore
  52. 2026-07-12 02:38 UTCVendor advisory
  53. 2026-07-11 22:23 UTCVendor advisory
  54. 2026-07-11 18:10 UTCVendor advisory
  55. 2026-07-11 13:57 UTCVendor advisory
  56. 2026-07-11 09:43 UTCVendor advisory
  57. 2026-07-11 08:25 UTCEPSS rescore
  58. 2026-07-11 08:25 UTCEPSS rescore
  59. 2026-07-11 05:29 UTCVendor advisory
  60. 2026-07-11 01:15 UTCVendor advisory
  61. 2026-07-10 21:00 UTCVendor advisory
  62. 2026-07-10 17:52 UTCCISA KEV update
  63. 2026-07-10 16:47 UTCVendor advisory
  64. 2026-07-10 12:33 UTCVendor advisory
  65. 2026-07-10 08:19 UTCVendor advisory
  66. 2026-07-10 04:06 UTCVendor advisory
  67. 2026-07-09 23:52 UTCVendor advisory
  68. 2026-07-09 19:39 UTCVendor advisory
  69. 2026-07-09 19:08 UTCEPSS rescore
  70. 2026-07-09 15:26 UTCVendor advisory
  71. 2026-07-09 11:12 UTCVendor advisory
  72. 2026-07-09 06:58 UTCVendor advisory
  73. 2026-07-09 02:44 UTCVendor advisory
  74. 2026-07-08 22:30 UTCVendor advisory
  75. 2026-07-08 18:17 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(6)

What is CVE-2022-4135?
CVE-2022-4135 is a critical vulnerability published on November 25, 2022. 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)
When was CVE-2022-4135 disclosed?
CVE-2022-4135 was first published in the National Vulnerability Database on November 25, 2022, with the most recent update on October 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-4135 actively exploited?
Yes. CISA added CVE-2022-4135 to the Known Exploited Vulnerabilities catalog on November 28, 2022, affecting Google Chromium GPU. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2022-4135?
CVE-2022-4135 has a CVSS v3 base score of 9.6 (NVD).
Which products are affected by CVE-2022-4135?
CVE-2022-4135 affects Google Chromium GPU. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2022-4135?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-4135, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-4135

Explore →

Is Your Infrastructure Affected by CVE-2022-4135?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs