Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2022-3653: Heap Buffer Overflow in Vulkan in Google Chrome <107.0.5304.62

Published Nov 1, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.8High · v3.1
EPSS0.83%59th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Google
IdentifiersCVE-2022-3653CWE-122

A heap buffer overflow vulnerability exists in the Vulkan component of Google Chrome prior to version 107.0.5304.62. The vulnerability can be triggered by a remote attacker through a crafted HTML page, leading to potential heap corruption. This issue is due to improper handling of memory boundaries in the Vulkan implementation within Chromium.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation of this vulnerability could allow a remote attacker to achieve heap corruption, which may lead to arbitrary code execution in the context of the browser. This could result in full compromise of the affected user's system if chained with other vulnerabilities or sandbox escapes.

Mitigation

If you can’t patch tonight, do this now.

As a temporary mitigation, users can disable WebGL or restrict access to untrusted web content. Employing browser sandboxing and keeping the browser up to date will reduce the risk of exploitation.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 107.0.5304.62 or later, where this vulnerability has been addressed by proper bounds checking and memory management in the Vulkan component.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication
FAQ

Frequently asked questions

Is CVE-2022-3653 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2022-3653 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2022-3653?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2022-3653, the earliest disclosed Jan 9, 2026.
Is there a patch for CVE-2022-3653?
Upgrade Google Chrome to version 107.0.5304.62 or later, where this vulnerability has been addressed by proper bounds checking and memory management in the Vulkan component.
What products are affected by CVE-2022-3653?
Google Chrome.
How severe is CVE-2022-3653?
CVE-2022-3653 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.83% (59th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.