How severe is CVE-2022-0609?

CVE-2022-0609 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-0609?

CVE-2022-0609 affects the following packages: CefSharp.Common (NuGet), CefSharp.OffScreen (NuGet), CefSharp.WinForms (NuGet), CefSharp.Wpf (NuGet), CefSharp.Wpf.HwndHost (NuGet), CefSharp.Common.NETCore (NuGet), CefSharp.OffScreen.NETCore (NuGet), CefSharp.WinForms.NETCore (NuGet), and 1 more. Ecosystems affected: NuGet.

How do I fix CVE-2022-0609?

Update CefSharp.Common to 98.1.210 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0609 is resolved across your whole dependency graph.

How do I detect CVE-2022-0609 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for CefSharp.Common. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2022-0609 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2022-0609?

O3 pinpoints whether CVE-2022-0609 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2022-0609 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2022-0609, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-0609?

CVE-2022-0609 has an EPSS (Exploit Prediction Scoring System) score of 22.0%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2022-0609 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2022-0609 (Google Chromium Animation Use-After-Free Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-02-15. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-03-01. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

When was CVE-2022-0609 published, and has it been updated?

CVE-2022-0609 was published on April 5, 2022 and was last updated on March 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-02-15 — agencies required to remediate by 2022-03-01

.NET NuGet

CVE-2022-0609

HIGH

Use after free in Animation

Also known asGHSA-vv6j-ww6x-54gx

Published

Apr 5, 2022

Updated

Mar 14, 2026

Affected

9 pkgs

Patched

9 / 9

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

22.0%probability of exploitation in next 30 days

Moderate Risk97th percentile-1.58%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

9 pkgs affected

.NETCefSharp.Common.NETCefSharp.OffScreen.NETCefSharp.WinForms.NETCefSharp.Wpf.NETCefSharp.Wpf.HwndHost.NETCefSharp.Common.NETCore.NETCefSharp.OffScreen.NETCore.NETCefSharp.WinForms.NETCore+1 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Use after free in Animation in Google Chrome prior to 98.0.4758.102 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Affected Packages

9 total 9 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`CefSharp.Common`	all versions	98.1.210
.NETNuGet	`CefSharp.OffScreen`	all versions	98.1.210
.NETNuGet	`CefSharp.WinForms`	all versions	98.1.210
.NETNuGet	`CefSharp.Wpf`	all versions	98.1.210
.NETNuGet	`CefSharp.Wpf.HwndHost`	all versions	98.1.210
.NETNuGet	`CefSharp.Common.NETCore`	all versions	98.1.210

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Use after free in Animation in Google Chrome prior to 98.0.4758.102 allo…

chromereleases.googleblog.comChromeFeb 2022

Use after free in Animation in Google Chrome prior to 98.0.4758.102 allo…

chromereleases.googleblog.comGoogle-sheetFeb 2022

Use after free in Animation in Google Chrome prior to 98.0.4758.102 allo…

cisa.govCISAFeb 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for CefSharp.Common. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update CefSharp.Common to 98.1.210 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0609 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-0609 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2022-0609. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Use after free in Animation in Google Chrome prior to 98.0.4758.102 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

O3 Security · Impact-Aware SCA

Is CVE-2022-0609 in your dependencies?

O3 detects CVE-2022-0609 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

CVE-2022-0609

EPSS Exploitation Probability

Blast Radius

Description

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is CVE-2022-0609 in your dependencies?