dbcve.org
ChromeWeb browser · Google

CVE-2026-12462

HIGH · 7.5 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to 149.0.7827.155 or later.
See remediation →
82/100
Remediation priority · High
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 Media in Google Chrome prior to 149.0.7827.155 allowed a remote attacker who had compromised the renderer process to execute arbitrary code inside a sandbox 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

Use-after-free vulnerability in Chrome's Media component prior to version 149.0.7827.155 allows a remote attacker with already-compromised renderer process to escape sandbox restrictions and execute arbitrary code via a malicious HTML page.

MitigationUpdate Google Chrome to version 149.0.7827.155 or later; for enterprise environments, deploy the update through patch management systems and verify complete coverage across 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:< 149.0.7827.155

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 Chrome installation: On Windows, look in C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. On macOS, check /Applications/Google Chrome.app. On Linux, run which google-chrome or check /usr/bin/google-chrome.
    Affected if Chrome is not installed on the system - no action needed.
  2. Determine installed Chrome version
    Open Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/help. The version number is displayed on this page.
    Affected if Unable to determine the version - manual investigation required.
  3. Compare version against affected range
    Compare the installed version number to 149.0.7827.155. Note the full version string (e.g., 149.0.7827.154 would be vulnerable, 149.0.7827.155 or higher would not be).
    Affected if Installed version is less than 149.0.7827.155 - the browser is vulnerable.
  4. Check for signs of renderer process compromise
    Review Chrome's crash reports in chrome://crashes, check for unexpected extensions or plugins, and look for anomalous processes. On enterprise systems, review endpoint detection logs for suspicious Chrome child processes.
    Affected if Signs of renderer compromise detected alongside vulnerable Chrome version - potential active exploitation.

A system is affected if Google Chrome is installed with a version lower than 149.0.7827.155, as this creates the condition where a compromised renderer process could exploit the use-after-free vulnerability to escape sandbox restrictions.

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

Update Google Chrome to version 149.0.7827.155 or later; for enterprise environments, deploy the update through patch management systems and verify complete coverage across endpoints.

Recommended fix High confidence

149.0.7827.155 or later

  1. Open Chrome and navigate to chrome://settings/help to check the current version
  2. If the version shown is earlier than 149.0.7827.155, click 'Update Google Chrome' to download and install the latest version
  3. Restart Chrome after the update completes to apply the fix

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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