dbcve.org
ChromeWeb browser · Google

CVE-2026-12019

HIGH · 8.3 CVSS v3.1 Published 2026-06-11
Fix available
A fix is available. Upgrade to 149.0.7827.115 or later.
See remediation →
90/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
Heap buffer overflow in Codecs in Google Chrome on Linux and ChromeOS prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 · moderate confidence

Heap buffer overflow vulnerability in the Codecs component of Google Chrome on Linux and ChromeOS. An attacker who has already compromised the renderer process can exploit this via a crafted HTML page to potentially escape the Chrome sandbox. Fixed in version 149.0.7827.115.

MitigationUpgrade Google Chrome on Linux and ChromeOS to version 149.0.7827.115 or later. Since exploitation requires a compromised renderer process, review existing endpoint protection and network monitoring to detect any ongoing compromises.

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.115

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/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 Google Chrome is installed on Linux or ChromeOS
    Check if Chrome is installed by looking for the chrome binary (e.g., /usr/bin/google-chrome, /usr/bin/chrome) or check the installed packages using package manager (dpkg -l | grep google-chrome or rpm -qa | grep google-chrome)
    Affected if Chrome is found on a Linux or ChromeOS system
  2. Retrieve the installed Chrome version
    Open Chrome and navigate to chrome://version, or run 'google-chrome --version' or 'google-chrome --product-version' from the command line
    Affected if Unable to retrieve a version number (Chrome may not be properly installed)
  3. Compare installed version against the fixed version
    Compare the version shown (e.g., 149.0.7827.115) against the affected range: any version less than 149.0.7827.115 on Linux or ChromeOS is vulnerable
    Affected if Installed version is lower than 149.0.7827.115 (for example, 148.0.6095.132)
  4. Verify the platform is Linux or ChromeOS
    Confirm the operating system is Linux or ChromeOS using 'uname -a' or checking /etc/os-release; this vulnerability only affects those platforms
    Affected if The system is running Chrome on Windows or macOS (these are NOT affected by this specific CVE)

A user is affected if Google Chrome on Linux or ChromeOS is installed with a version lower than 149.0.7827.115, as the heap buffer overflow in the Codecs component can be exploited by an attacker who has already compromised the renderer process.

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.115 or later
Fixed in 149.0.7827.115
Interim mitigation

Upgrade Google Chrome on Linux and ChromeOS to version 149.0.7827.115 or later. Since exploitation requires a compromised renderer process, review existing endpoint protection and network monitoring to detect any ongoing compromises.

Recommended fix High confidence

149.0.7827.115 or later

  1. Open Google Chrome browser
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Settings' from the dropdown menu
  4. In the Settings page, click 'About Chrome' in the left sidebar
  5. Chrome will automatically check for updates; if 149.0.7827.115 or later is available, click 'Update Chrome'
  6. Restart the browser to apply the update
  7. Verify the update by returning to About Chrome to confirm the installed version
Caveat Chrome updates are typically seamless; minimal risk of extension or settings incompatibility

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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