dbcve.org
ChromeWeb browser · Google

CVE-2026-11636

HIGH · 7.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 149.0.7827.103 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 Autofill in Google Chrome on Windows prior to 149.0.7827.103 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption 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 · moderate confidence

Use after free vulnerability in Google Chrome's Autofill feature on Windows allows a remote attacker to execute arbitrary code via heap corruption. Exploitation requires the victim to perform specific UI gestures on a crafted HTML page, making user interaction a necessary condition for attack success.

MitigationUpdate Google Chrome to version 149.0.7827.103 or later to patch the vulnerability. Organizations should deploy the browser update through standard patch management processes and verify Autofill functionality post-update.

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
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 Chrome is installed
    Check for Chrome executable at C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. Alternatively, open Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome"
    Affected if Chrome is not installed on the Windows system
  2. Determine installed Chrome version
    Open Chrome and navigate to chrome://version, or run "C:\Program Files\Google\Chrome\Application\chrome.exe" --version from Command Prompt, or read the Version value from the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome
    Affected if Unable to retrieve the version number
  3. Compare version against affected range
    Review the version number obtained from the previous step. The affected version range is any version less than 149.0.7827.103. Compare numerically: for example, 149.0.7827.100 is affected, 149.0.7827.103 is not
    Affected if Installed version is less than 149.0.7827.103 (for example, 148.0.XXXX or 149.0.7827.102)
  4. Confirm Autofill is enabled
    In Chrome, go to Settings > Autofill and passwords > Autofill settings, or navigate to chrome://settings/autofill. Verify if any Autofill profiles or payment methods are saved and enabled
    Affected if Autofill is enabled with saved data (the vulnerability specifically targets the Autofill feature)

A user is affected if Google Chrome for Windows is installed with a version lower than 149.0.7827.103 and Autofill is enabled, as the use-after-free vulnerability requires the Autofill feature to be active.

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 patch the vulnerability. Organizations should deploy the browser update through standard patch management processes and verify Autofill functionality post-update.

Recommended fix High confidence

149.0.7827.103 or later

  1. Open Google Chrome on Windows
  2. Click the three-dot menu (top right) and select 'Settings'
  3. Scroll down and click 'About Chrome' in the left sidebar
  4. Chrome will automatically check for updates; if version 149.0.7827.103 or later is available, it will download and install
  5. Restart Chrome to complete the update
  6. Alternatively, download the latest Chrome installer from google.com/chrome and run it to upgrade

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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