CVE-2022-4135
Google Chromium GPU Heap Buffer Overflow
- Published25 Nov 2022
- Added to CISA KEV28 Nov 2022
- Remediation due19 Dec 2022
Description
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 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2022-4135 being actively exploited?
Yes. CVE-2022-4135 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 28 Nov 2022.
How severe is CVE-2022-4135?
CVE-2022-4135 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 31.9% probability of exploitation.
Which products are affected by CVE-2022-4135?
Affected products include Google Chrome, Microsoft Edge, Microsoft Edge Chromium.
How do I fix CVE-2022-4135?
Upgrade affected software to a fixed version, for example Google Chrome 107.0.5304.121, Microsoft Edge 107.0.1418.62, Microsoft Edge Chromium 107.0.5304.150 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2022-4135 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.