ChromeWeb browser · Google
CVE-2026-11135
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 · uneditedInsufficient policy enforcement in Autofill in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to bypass discretionary access control 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 · moderate confidenceInsufficient policy enforcement in Google Chrome's Autofill feature prior to version 149.0.7827.53 allows a remote attacker to bypass discretionary access control mechanisms via a crafted HTML page. This client-side vulnerability enables a malicious webpage to improperly access or manipulate autofill data beyond its intended security boundaries.
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.53CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Google Chrome is installedCheck for Google Chrome on the system. On Windows, look for Chrome in Program Files or via the registry. On macOS, check /Applications for Google Chrome.app. On Linux, check common package manager locations.Affected if Chrome browser is not present on the system - no further action needed
-
Determine installed Chrome versionOpen Chrome, navigate to Settings > Help > About Google Chrome, or type chrome://version in the address bar. Record the version number displayed (e.g., 149.0.7827.53).Affected if Version is less than 149.0.7827.53 (for example, 149.0.7827.52, 148.x.x.x, etc.)
-
Confirm Autofill feature is enabledIn Chrome settings, go to Settings > Autofill and passwords > Autofill settings, or navigate to chrome://settings/autofill. Verify if any Autofill options are turned on (addresses, passwords, credit cards, etc.).Affected if Any Autofill categories are enabled (toggle is ON) - this is the feature affected by the vulnerability
-
Check for recent browser activityReview browser history or ask users if they have recently visited untrusted or unfamiliar websites, especially those that could contain specially crafted HTML pages designed to exploit this flaw.Affected if User has recently browsed untrusted websites while using a vulnerable Chrome version with Autofill enabled
You are affected if Chrome is installed with a version prior to 149.0.7827.53 AND the Autofill feature is enabled, as the vulnerability requires both conditions to be exploitable.
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.53
Update Google Chrome to version 149.0.7827.53 or later to obtain the patch for this Autofill policy enforcement vulnerability.
Chrome 149.0.7827.53 or later
- Open Google Chrome
- Navigate to Settings > Help > About Google Chrome
- Chrome will automatically check for updates and download version 149.0.7827.53 or later
- Restart Chrome to apply the update
- Verify the version by returning to About Google Chrome and confirming the version is 149.0.7827.53 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11135 — 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-11135 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