dbcve.org
ChromeWeb browser · Google

CVE-2026-3062

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-23
Fix available
A fix is available. Upgrade to 145.0.7632.116 / 145.0.7632.117 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 read and write in Tint in Google Chrome on Mac prior to 145.0.7632.116 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

Out of bounds memory read/write vulnerability in Tint (Google's shader translator) in Google Chrome on Mac prior to version 145.0.7632.116 allows remote attackers to achieve arbitrary memory access and potential code execution via a malicious crafted HTML page.

MitigationUpdate Google Chrome for Mac to version 145.0.7632.116 or later to remediate the 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:< 145.0.7632.116< 145.0.7632.117

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Confirm operating system is macOS
    Run 'uname -s' in terminal or check System Settings > About to verify the OS is Darwin/macOS. This vulnerability only affects Chrome on Mac, not other platforms.
    Affected if The system is running macOS - if running Windows, Linux, or Chrome OS, this CVE does not apply.
  2. Verify Google Chrome is installed
    Run 'ls /Applications/Google Chrome.app' in terminal or check the Applications folder for Google Chrome. Alternatively, run 'chromium --version' or 'google-chrome --version' if available.
    Affected if Google Chrome is not installed - if the browser is not present, the system is not affected.
  3. Check installed Chrome version on Mac
    Open Google Chrome, click Chrome menu > About Google Chrome. Alternatively, run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' in terminal.
    Affected if Unable to determine version - if Chrome cannot be queried for its version, the check is inconclusive.
  4. Compare version against affected range
    Compare the installed version number to 145.0.7632.116 (the lower of the two affected versions). Versions below this number are vulnerable.
    Affected if Installed version is less than 145.0.7632.116 - for example, 145.0.7632.115, 144.x.x.x, or any earlier version indicates the system is affected by this vulnerability.

The system is affected if running Google Chrome on macOS with a version number lower than 145.0.7632.116.

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.116 / 145.0.7632.117 or later
Fixed in 145.0.7632.116145.0.7632.117
Interim mitigation

Update Google Chrome for Mac to version 145.0.7632.116 or later to remediate the vulnerability.

Recommended fix High confidence

Google Chrome 145.0.7632.116 (or later stable release for Mac)

  1. 1. Open Google Chrome on the affected Mac system
  2. 2. Click on the three-dot menu icon in the top-right corner
  3. 3. Select 'Help' from the dropdown menu
  4. 4. Click on 'About Google Chrome'
  5. 5. Chrome will check for updates automatically; if an update is available, it will begin downloading
  6. 6. Wait for the download to complete, then click 'Relaunch' to restart Chrome and apply the update
  7. 7. Verify the update by returning to 'About Google Chrome' and confirm the version number is 145.0.7632.116 or higher

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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