# CVE-2022-0609: Google Chromium Animation Use-After-Free > A remote attacker can exploit heap corruption via a crafted HTML page due to a use-after-free flaw in Google Chrome's Animation component. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Yes, since 15 Feb 2022 (CISA KEV) - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 4 Apr 2022 - **Updated:** 21 Oct 2025 - **Also known as:** CLEANSTART-2024-IP77496, DEBIAN-CVE-2022-0609, GHSA-vv6j-ww6x-54gx, UBUNTU-CVE-2022-0609 ## What is CVE-2022-0609? CVE-2022-0609 is a high-severity use after free vulnerability in Google Chrome, published on 4 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official 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. Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2022-0609? 18 open source packages ship an affected version, including CefSharp.Common, CefSharp.Common.NETCore and CefSharp.OffScreen. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `CefSharp.Common` | NuGet | All versions | 98.1.210 | | `CefSharp.Common` | NuGet | All versions | 98.1.210 | | `CefSharp.Common.NETCore` | NuGet | All versions | 98.1.210 | | `CefSharp.Common.NETCore` | NuGet | All versions | 98.1.210 | | `CefSharp.OffScreen` | NuGet | All versions | 98.1.210 | | `CefSharp.OffScreen` | NuGet | All versions | 98.1.210 | | `CefSharp.OffScreen.NETCore` | NuGet | All versions | 98.1.210 | | `CefSharp.OffScreen.NETCore` | NuGet | All versions | 98.1.210 | | `CefSharp.WinForms` | NuGet | All versions | 98.1.210 | | `CefSharp.WinForms` | NuGet | All versions | 98.1.210 | | `CefSharp.WinForms.NETCore` | NuGet | All versions | 98.1.210 | | `CefSharp.WinForms.NETCore` | NuGet | All versions | 98.1.210 | | `CefSharp.Wpf` | NuGet | All versions | 98.1.210 | | `CefSharp.Wpf` | NuGet | All versions | 98.1.210 | | `CefSharp.Wpf.HwndHost` | NuGet | All versions | 98.1.210 | | `CefSharp.Wpf.HwndHost` | NuGet | All versions | 98.1.210 | | `CefSharp.Wpf.NETCore` | NuGet | All versions | 98.1.210 | | `CefSharp.Wpf.NETCore` | NuGet | All versions | 98.1.210 | Products: Google Chrome. ## How do I fix CVE-2022-0609? Upgrade CefSharp.Common to 98.1.210 or later. US federal agencies must fix it by 1 Mar 2022. ## Is CVE-2022-0609 being exploited? Yes. Attackers have exploited CVE-2022-0609 in the wild since at least 15 Feb 2022. ## Other vulnerabilities in Google Chrome - [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild) - [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild) - [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild) - [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild) - [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-0609 and fix it if it is affected. What it is: CVE-2022-0609 is a high-severity use after free vulnerability in Google Chrome, published on 4 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: Yes. Attackers have exploited CVE-2022-0609 in the wild since at least 15 Feb 2022. Affected packages and fixed versions: - CefSharp.Common (NuGet): affected all versions; fixed in 98.1.210 - CefSharp.Common (NuGet): affected all versions; fixed in 98.1.210 - CefSharp.Common.NETCore (NuGet): affected all versions; fixed in 98.1.210 - CefSharp.Common.NETCore (NuGet): affected all versions; fixed in 98.1.210 - CefSharp.OffScreen (NuGet): affected all versions; fixed in 98.1.210 - CefSharp.OffScreen (NuGet): affected all versions; fixed in 98.1.210 - CefSharp.OffScreen.NETCore (NuGet): affected all versions; fixed in 98.1.210 - CefSharp.OffScreen.NETCore (NuGet): affected all versions; fixed in 98.1.210 - CefSharp.WinForms (NuGet): affected all versions; fixed in 98.1.210 - CefSharp.WinForms (NuGet): affected all versions; fixed in 98.1.210 - CefSharp.WinForms.NETCore (NuGet): affected all versions; fixed in 98.1.210 - CefSharp.WinForms.NETCore (NuGet): affected all versions; fixed in 98.1.210 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-0609/ (Markdown: https://insights.sbomify.com/CVE-2022-0609/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0609 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0609 - OSV: https://osv.dev/vulnerability/CVE-2022-0609 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-0609/ Summaries are generated and may contain mistakes; the official description above is the record.