dbcve.org
ChromeWeb browser · Google

CVE-2026-11209

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Inappropriate implementation in Passwords in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)

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

Inappropriate implementation in Google Chrome's Passwords manager prior to version 149.0.7827.53 allows a remote attacker who has already compromised the renderer process to obtain potentially sensitive information from process memory through a crafted HTML page.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later. This is a client-side browser vulnerability where the attacker requires a pre-compromised renderer process.

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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. Check if Google Chrome is installed
    On Windows: Check for Chrome in Program Files or via 'chrome --version' in command prompt. On macOS: Check /Applications/Google Chrome.app or run '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version'. On Linux: Run 'google-chrome --version' or 'chromium-browser --version'.
    Affected if Google Chrome is installed and the version is below 149.0.7827.53
  2. Verify the installed Chrome version
    Navigate to chrome://settings/help in the Chrome address bar, or run 'google-chrome --version' from command line. Compare the displayed version number against 149.0.7827.53.
    Affected if Version shown is less than 149.0.7827.53
  3. Confirm Password Manager feature is enabled
    Go to chrome://settings/passwords in Chrome. Verify that 'Offer to save passwords' or 'Google Password Manager' toggle is enabled. This feature is enabled by default.
    Affected if Password Manager is enabled (which is the default state)
  4. Assess renderer process compromise risk
    Review browser for unexpected extensions, unusual startup behavior, or signs of malware infection. This vulnerability requires a pre-compromised renderer, so investigate any indicators of compromise.
    Affected if There are signs of renderer process compromise or malware on the system

A user is affected if they have Google Chrome installed with a version below 149.0.7827.53 and the Passwords manager feature is enabled, particularly if there is any indication the renderer process may be compromised.

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.53 or later
Fixed in 149.0.7827.53
Interim mitigation

Update Google Chrome to version 149.0.7827.53 or later. This is a client-side browser vulnerability where the attacker requires a pre-compromised renderer process.

Recommended fix High confidence

149.0.7827.53

  1. Open Google Chrome browser
  2. Navigate to Chrome menu (three dots) > Help > About Google Chrome
  3. The browser will check for updates automatically
  4. If version is below 149.0.7827.53, click 'Update Google Chrome'
  5. Restart the browser to complete the update
  6. Verify the update by returning to Help > About Google Chrome and confirming version 149.0.7827.53 or later

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-11209 — 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-11209 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