dbcve.org
ChromeWeb browser · Google

CVE-2026-2317

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 145.0.7632.45 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Inappropriate implementation in Animation in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)

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 · moderate confidence

This is a cross-origin information disclosure vulnerability in Google Chrome's Animation implementation. A remote attacker could exploit this flaw via a maliciously crafted HTML page to leak data from other origins, bypassing same-origin policy protections.

MitigationUpdate Google Chrome to version 145.0.7632.45 or later to patch the vulnerable Animation component.

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:< 145.0.7632.45

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
None
Availability
None

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

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 Chrome version
    Open Google Chrome, click the three-dot menu in the top-right corner, navigate to Help > About Google Chrome, or directly go to chrome://settings/help to see the current version number
    Affected if The displayed version is below 145.0.7632.45
  2. Verify version via command line
    Run 'chrome --version' in command prompt or terminal, or check the file properties of chrome.exe in the Chrome installation directory
    Affected if The reported version number is less than 145.0.7632.45

If the installed Google Chrome version is lower than 145.0.7632.45, the browser is vulnerable to cross-origin information disclosure via the Animation component.

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 145.0.7632.45 or later
Fixed in 145.0.7632.45
Interim mitigation

Update Google Chrome to version 145.0.7632.45 or later to patch the vulnerable Animation component.

Recommended fix High confidence

Chrome 145.0.7632.45 or later

  1. Open Google Chrome browser
  2. Navigate to Chrome menu (three dots) > Help > About Google Chrome
  3. Verify the current version number
  4. If the version is earlier than 145.0.7632.45, click 'Update Google Chrome' to install the latest version
  5. Restart the browser after the update completes
Caveat Browser updates typically have minimal breaking changes; users may need to re-authenticate to some web services after update

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2317 — 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-2026-2317 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