Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2022-2294: WebRTC Heap Buffer Overflow in Google Chrome

Published Jul 28, 2022 · Updated 20 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.8High · v3.1
EPSS70.8%99th percentile
CISA KEVYesAdded Aug 25, 2022
In the wildActivePer CISA KEV
Vendors
GoogleFedora ProjectAppleWebkitgtkWebrtc ProjectWPE WebKit
IdentifiersCVE-2022-2294CWE-122

CVE-2022-2294 is a heap-based buffer overflow in the WebRTC component of Google Chrome versions before 103.0.5060.114. A remote attacker can trigger heap corruption through a crafted HTML page, potentially executing arbitrary code within the browser renderer process. Exploitation attributed to Candiru was documented in July 2022 against users in the Middle East, including delivery through a compromised Lebanese news-agency website.

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 can execute attacker-controlled shellcode within the Chrome renderer process. This compromises the affected process and can serve as an initial stage in a broader spyware infection chain. The vulnerability alone does not establish a browser sandbox escape, operating-system privilege escalation, or unrestricted host compromise.

Mitigation

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

Use threat hunting for known exploitation and spyware indicators, employee awareness training, and separation of personal and corporate devices to reduce exposure and support detection. Link-awareness measures alone are insufficient because exploitation has involved compromised legitimate websites. These measures do not correct the underlying vulnerability or replace updating Chrome.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 103.0.5060.114 or later. Prefer the latest supported release and restart the browser to ensure the updated executable is running.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
AppleIpadosoperating_system
AppleIphone Osoperating_system
AppleMac Os Xoperating_system
AppleMacosoperating_system
AppleTvosoperating_system
AppleWatchosoperating_system
Fedora ProjectExtra Packages For Enterprise Linuxapplication
Fedora ProjectFedoraoperating_system
GoogleChromeapplication
WebkitgtkWebkitgtkapplication
Webrtc ProjectWebrtcapplication
WPE WebKitWpe Webkitapplication
FAQ

Frequently asked questions

Is CVE-2022-2294 exploited in the wild?
Yes. As of Oct 28, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Aug 25, 2022.
Is there a public exploit for CVE-2022-2294?
As of Oct 28, 2026, Mallory has found no public exploit for CVE-2022-2294.
Is there a patch for CVE-2022-2294?
Upgrade Google Chrome to version 103.0.5060.114 or later. Prefer the latest supported release and restart the browser to ensure the updated executable is running.
What products are affected by CVE-2022-2294?
Google Chrome, Webrtc Project Webrtc, Fedora Project Extra Packages For Enterprise Linux, Fedora Project Fedora, Apple Ipados, and 7 more.
How severe is CVE-2022-2294?
CVE-2022-2294 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 70.8% (99th percentile) as of Oct 28, 2026.
Activity feed

Recent activity

7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+1 more in the timeline. Sign up to see them
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 evidence4Every report linking this CVE to a named adversary.
Associated malware4Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, 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.