dbcve.org
ChromeWeb browser · Google

CVE-2026-11638

CRITICAL · 9.6 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 149.0.7827.103 or later.
See remediation →
100/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
Use after free in Printing in Google Chrome prior to 149.0.7827.103 allowed a remote attacker 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 confidence

Use-after-free vulnerability in Google Chrome's Printing component prior to version 149.0.7827.103 allows a remote attacker to potentially escape the sandbox via a crafted HTML page. The memory safety flaw occurs when memory is accessed after being freed, potentially enabling arbitrary code execution.

MitigationUpdate Google Chrome to version 149.0.7827.103 or later to address the vulnerability. Ensure browser update policies are enforced across affected systems.

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

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

CVSS:3.1/AV:N/AC:L/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. Verify Chrome browser is installed
    Check for Chrome executable: on Windows look in C:\Program Files\Google\Chrome\Application\, on macOS check /Applications/Google Chrome.app, on Linux run 'which google-chrome' or 'which chromium-browser'
    Affected if Google Chrome or Chromium browser is found on the system
  2. Determine installed Chrome version
    Open Chrome, type chrome://settings/help in the address bar and press Enter, or run 'google-chrome --version' from command line
    Affected if Displayed version number is lower than 149.0.7827.103 (for example 148.x.x.x or earlier)
  3. Confirm printing functionality is present
    The printing component is built into Chrome by default; verify by opening any webpage and pressing Ctrl+P (Windows/Linux) or Cmd+P (macOS) to access print preview
    Affected if Print dialog opens successfully, indicating the printing component is active
  4. Check if Chrome is used with sandbox enabled
    In Chrome, navigate to chrome://sandbox to view the sandbox status for each renderer process
    Affected if Chrome is running (the vulnerability exists in the printing component regardless of sandbox state, but successful exploitation could allow sandbox escape)

You are affected if Chrome or Chromium is installed with a version lower than 149.0.7827.103 and the browser is actively used.

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.103 or later
Fixed in 149.0.7827.103
Interim mitigation

Update Google Chrome to version 149.0.7827.103 or later to address the vulnerability. Ensure browser update policies are enforced across affected systems.

Recommended fix High confidence

149.0.7827.103 or later

  1. Open Google Chrome
  2. Click the three-dot menu in the top-right corner
  3. Select 'Settings'
  4. Click 'About Chrome' in the left sidebar
  5. Chrome will automatically check for updates and display the current version
  6. If an update is available, click 'Update Google Chrome'
  7. Restart Chrome to complete the update
  8. Verify the version is 149.0.7827.103 or later by returning to About Chrome

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
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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