Vulnerability report

Exploited in the wild Confirmed confidence In CISA KEV

CVE-2022-4135

Chrome

Google / Chrome · affected before 107.0.5304.121

Watch CVE-2022-4135 Browse KEV feed
Severity
CVSS 9.6 · Critical
Confidence
Confirmed
Exploit status
Exploited in the wild
EPSS
31.9%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2022-4135 is an unauthenticated vulnerability affecting Google Chrome. 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...

Is it exploited?

Yes. Previdian tracks this CVE as a known exploited vulnerability. Confidence is confirmed. Listed in CISA KEV.

Who is affected?

Google / Chrome affected before 107.0.5304.121.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

Chrome

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)

Google Affected
Chrome
Before 107.0.5304.121
View vendor advisory (opens in new tab)
Published
25 Nov 2022
Exploitation Reported
28 Nov 2022
Attack vector
Remote
Complexity
Low
Privileges
None
User interaction
Required

Tags

cisa nessus_scanner

CVE References

Exploitation evidence

Why Previdian marks this CVE as exploited

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploited in the wild

CISA

Recorded 28 Nov 2022

A trusted third party reported exploitation.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CISA First 2022-11-28 00:00 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Observed signals

Request targets
User-Agents
Callback hosts
0
0
0

Request targets and User-Agents available in Pro. Callback host details available in Enterprise.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

Scanner Artifacts

Scanner and exploit-framework references linked to this CVE.

Scanner Reference Detected
Nessus https://www.tenable.com/plugins/nessus/175034 02 Jun 2025

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

9.6 Critical

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

EPSS

31.9%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Weaknesses

Out-of-bounds Write CWE-787

Timeline

From disclosure to observed exploitation

  1. 09:27 UTC

    Nessus plugin available

    Scanner coverage available

  2. 00:00 UTC

    Added to CISA KEV

    Listed in the CISA Known Exploited Vulnerabilities catalog

  3. 00:00 UTC

    CVE published

    Vulnerability disclosed publicly

  4. 00:00 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

Start 14-day Pro trial Read API docs
  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2022-4135

Free JSON includes basic KEV fields 
{
  "cve_id": "CVE-2022-4135",
  "confidence": "Confirmed",
  "cvss_score": 9.6,
  "cvss_estimated": false,
  "epss_score": 0.31864,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}