ChromeWeb browser · Google
CVE-2026-11640
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 · uneditedInteger overflow in libyuv in Google Chrome prior to 149.0.7827.103 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 confidenceInteger overflow vulnerability in the libyuv library (used for video/image processing) in Google Chrome versions prior to 149.0.7827.103. A remote attacker who has already compromised the renderer process can exploit this overflow via a crafted HTML page to potentially escape Chrome's sandbox isolation. CVSS 8.3 reflects the high impact of sandbox escape combined with the pre-condition of renderer compromise.
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
< 149.0.7827.103CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Chrome versionOpen Chrome, click the three-dot menu, go to Help > About Google Chrome, or navigate to chrome://settings/helpAffected if The displayed version number is lower than 149.0.7827.103
-
Verify Chrome version via command line (optional)On Windows, run 'chrome --version' or check the file version of chrome.dll. On macOS, run '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version'Affected if The reported version is less than 149.0.7827.103
If the installed Google Chrome version is below 149.0.7827.103, the environment is vulnerable to the libyuv integer overflow that could allow sandbox escape.
Generated from the published advisory. Verify against your own configuration.
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 · scoped149.0.7827.103
Upgrade Google Chrome to version 149.0.7827.103 or later to patch the integer overflow in libyuv; organizations should also investigate how the renderer process was initially compromised as the pre-condition indicates an existing security incident.
Chrome version 149.0.7827.103 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Alternatively, navigate to chrome://settings/help in the address bar
- Chrome will automatically check for and download the latest update
- If version 149.0.7827.103 or later is available, wait for the download to complete
- Click 'Restart' or 'Relaunch' to apply the update
- Verify the update by returning to chrome://settings/help and confirming the version is 149.0.7827.103 or later
- For enterprise deployments, use Group Policy or the Chrome Enterprise bundle to push version 149.0.7827.103 or later to managed devices
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11640 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-11640 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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