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 2 Jan 2026.
ChromeWeb browser · Google

CVE-2025-14174

HIGH · 8.8 CVSS v3.1 Published 2025-12-12
Fix available
A fix is available. Upgrade to 18.7.3 / 26.2 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
Out of bounds memory access in ANGLE in Google Chrome on Mac prior to 143.0.7499.110 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)

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

This is an out-of-bounds memory access vulnerability in ANGLE (a graphics rendering library) within Google Chrome on macOS. A remote attacker can exploit this by luring a user to visit a crafted malicious HTML page, potentially leading to memory corruption, information disclosure, or arbitrary code execution.

MitigationUpdate Google Chrome on macOS to version 143.0.7499.110 or later to remediate this vulnerability.

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:>= 143.0.7499.41, < 143.0.7499.110>= 143.0.7499.40, < 143.0.7499.109<= 143.0.7499.40
SafariWeb browser
Affected:< 26.2
IpadosOperating system
Affected:< 18.7.3>= 26.0, < 26.2
Iphone OsOperating system
Affected:< 18.7.3>= 26.0, < 26.2
macOSOperating system
Affected:< 26.2
TvosOperating system
Affected:< 26.2
VisionosOperating system
Affected:< 26.2
WatchosOperating system
Affected:< 26.2

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 Google Chrome version on macOS
    Open Chrome, click the three-dot menu, go to Help > About Google Chrome. Alternatively, navigate to chrome://version in the address bar.
    Affected if Version is between 143.0.7499.40 and 143.0.7499.109 inclusive, or exactly 143.0.7499.40 or below (specifically versions >= 143.0.7499.41 but < 143.0.7499.110, or >= 143.0.7499.40 but < 143.0.7499.109, or <= 143.0.7499.40)
  2. Check Safari version on macOS
    Open Safari, go to Safari > About Safari. The version number is displayed in the pop-up window.
    Affected if Version is below 26.2 (any version less than 26.2)
  3. Check macOS version for Safari vulnerability context
    Open System Settings > General > About, or run 'sw_vers' in Terminal.
    Affected if macOS version is below 26.2 (the underlying OS is vulnerable, affecting bundled Safari)

You are affected if Google Chrome versions 143.0.7499.40 through 143.0.7499.109 are running on macOS, or if Safari version is below 26.2 on macOS versions below 26.2.

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 18.7.3 / 26.2 / 143.0.7499.109 or later
Fixed in 18.7.326.2143.0.7499.109
Interim mitigation

Update Google Chrome on macOS to version 143.0.7499.110 or later to remediate this vulnerability.

Recommended fix High confidence

Chrome: 143.0.7499.110 or later | Safari/Apple products: 26.2 or later (or 18.7.3 for iOS/iPadOS < 26.0)

  1. For Chrome: Navigate to chrome://settings/help or use the Chrome menu > Help > About Google Chrome to check your current version
  2. If Chrome version is less than 143.0.7499.110, allow Chrome to automatically update or manually download the latest version from google.com/chrome
  3. For Safari on macOS: Open System Settings > General > Software Update and install any available updates
  4. For iOS/iPadOS devices: Go to Settings > General > Software Update and install any available updates
  5. For other Apple platforms (tvOS, watchOS, visionOS): Check for software updates through their respective Settings menus
  6. After updating, restart the browser/application to ensure the patch is fully applied
  7. Verify the version has been updated to 143.0.7499.110 or later for Chrome, and 26.2 or later for Apple products
Caveat Standard browser update; ensure compatibility with any site-specific browser plugins or enterprise policies before deploying

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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