dbcve.org
ChromeWeb browser · Google

CVE-2025-9478

HIGH · 8.8 CVSS v3.1 Published 2025-08-26
Fix available
A fix is available. Upgrade to 139.0.7258.154 or later.
See remediation →
95/100
Remediation priority · Urgent
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 ANGLE in Google Chrome prior to 139.0.7258.154 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)

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 ANGLE (a graphics abstraction layer used by Chrome for WebGL) allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. The flaw exists in the graphics rendering pipeline prior to Chrome version 139.0.7258.154.

MitigationUpdate Google Chrome to version 139.0.7258.154 or later to patch the ANGLE use-after-free vulnerability. Organizations should prioritize updating end-user systems given the CVSS 8.8 severity and remote exploitation potential.

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

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. Verify Google Chrome is installed
    Check for Google Chrome on the system - on Windows look in Program Files or via registry, on macOS check /Applications, on Linux check common package locations or via package manager (dpkg/rpm)
    Affected if Google Chrome is found on the system (proceed to version check)
  2. Determine installed Chrome version
    Open chrome://version in the Google Chrome browser and note the version string, or use system commands: on Windows 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v Version' or on macOS 'defaults read /Applications/Google\ Chrome.app/Contents/Info.plist CFBundleShortVersionString', on Linux 'google-chrome --version' or check via package manager
    Affected if Unable to retrieve version information (requires manual check via chrome://version)
  3. Compare version against affected range
    Parse the version number from step 2 and compare it to 139.0.7258.154 using semantic version comparison - ensure the full four-part version number is compared (139.0.7258.154)
    Affected if Installed version is less than 139.0.7258.154 (e.g., 139.0.7258.100, 138.x.x.x, or any earlier version)
  4. Check if ANGLE/WebGL is in use
    This vulnerability affects ANGLE (the graphics library used for WebGL rendering). Chrome uses ANGLE automatically for WebGL content. No configuration check needed - if Chrome is used for web browsing with WebGL content, the attack surface exists
    Affected if Chrome with vulnerable version is used to render WebGL content (which Chrome does automatically)

The environment is affected if Google Chrome is installed with any version lower than 139.0.7258.154 and is used for web browsing (WebGL rendering is enabled by default in Chrome).

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

Update Google Chrome to version 139.0.7258.154 or later to patch the ANGLE use-after-free vulnerability. Organizations should prioritize updating end-user systems given the CVSS 8.8 severity and remote exploitation potential.

Recommended fix High confidence

Chrome 139.0.7258.154 or later

  1. Open Google Chrome and navigate to Settings > About Chrome (or enter chrome://settings/help in the address bar)
  2. Chrome will automatically check for updates; if an update is available, click 'Update Google Chrome'
  3. Restart the browser to apply the update
  4. Alternatively, on Windows/macOS, you can update via the Chrome menu > Help > About Google Chrome
  5. On Linux systems, use your system package manager (e.g., sudo apt-get update && sudo apt-get upgrade google-chrome-stable for Debian/Ubuntu)
  6. On macOS, use the Software Update feature or download the latest version from google.com/chrome
Caveat Chrome updates typically do not introduce breaking changes for web applications; however, minor web compatibility regressions may occur with legacy content

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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