dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 1 Mar 2022.
ChromeWeb browser · Google

CVE-2022-0609

HIGH · 8.8 CVSS v3.1 Published 2022-04-05
Fix available
A fix is available. Upgrade to 98.0.4758.102 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Use-after-free vulnerability in Chrome's Animation component allows a remote attacker to corrupt the heap via a crafted HTML page, potentially enabling arbitrary code execution. The vulnerability exists in versions prior to 98.0.4758.102 and stems from improper memory management during animation processing.

MitigationUpdate Google Chrome to version 98.0.4758.102 or later to patch the vulnerability. Organizations should deploy the browser update through enterprise software distribution mechanisms and verify completion across all endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 98.0.4758.102

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Google Chrome version
    Navigate to chrome://version in the Chrome browser or run 'google-chrome --version' (Linux) or 'chrome --version' (Windows) from command line
    Affected if Version is below 98.0.4758.102
  2. Verify Chrome runtime version on Windows
    Open Windows Control Panel > Programs and Features, find Google Chrome, and note the version number listed
    Affected if Version shown is lower than 98.0.4758.102
  3. Check Chrome version on macOS
    Click Chrome menu > About Google Chrome, or run '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version' in Terminal
    Affected if Version displayed is below 98.0.4758.102

You are affected if the installed Google Chrome version is any release prior to 98.0.4758.102, as the use-after-free in the Animation component exists in all earlier versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 98.0.4758.102 or later
Fixed in 98.0.4758.102
Interim mitigation

Update Google Chrome to version 98.0.4758.102 or later to patch the vulnerability. Organizations should deploy the browser update through enterprise software distribution mechanisms and verify completion across all endpoints.

Recommended fix High confidence

Chrome 98.0.4758.102 or later

  1. Open Google Chrome browser
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' > 'About Google Chrome'
  4. Chrome will automatically check for updates; if an update is available, the browser will download it
  5. Verify the installed version is 98.0.4758.102 or later
  6. Restart Chrome if the update was not automatically applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-0609 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-0609 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data