ChromeWeb browser · Google
CVE-2026-11131
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 · uneditedUse after free in Autofill in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 confidenceUse-after-free vulnerability in Google Chrome for Android's Autofill component. A remote attacker with a compromised renderer process can exploit freed memory through a crafted HTML page, potentially achieving sandbox escape.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the browser and platformConfirm you are using Google Chrome on Android. Check the browser name in Chrome's settings under 'About Chrome' or check your device's app information for the Chrome package.Affected if The device is running Google Chrome on Android (this CVE does not affect Chrome on iOS, desktop Chrome, or other browsers).
-
Determine the installed Chrome versionOpen Chrome, tap the three-dot menu, go to Settings > About Chrome. Note the version number displayed (e.g., 149.0.7827.53).Affected if The version shown is any version prior to 149.0.7827.53 (e.g., 148.x.x.x or earlier).
-
Verify Autofill is enabledIn Chrome, go to Settings > Passwords and autofill > Autofill settings. Confirm the Autofill service is turned on.Affected if Autofill for addresses, payment methods, or passwords is enabled - the vulnerability exists in the Autofill component.
-
Check if renderer process compromise is possibleThis CVE requires an attacker to have already compromised the renderer process. Assess if the device has been exposed to malicious web content or if the user frequently visits untrusted websites.Affected if The device has been exposed to potentially malicious web content while using Chrome on Android.
You are affected if you are running Chrome on Android with a version lower than 149.0.7827.53 and have Autofill enabled on your device.
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 on Android to version 149.0.7827.53 or later to patch the vulnerability.
Chrome 149.0.7827.53 or later for Android
- Open the Google Play Store app on your Android device
- Search for 'Google Chrome' or locate it in your installed apps
- If an update is available, tap the 'Update' button to install version 149.0.7827.53 or later
- Alternatively, enable auto-updates for Chrome in Play Store settings to ensure future security updates are applied automatically
- Restart Chrome after the update completes to ensure all components are updated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11131 — 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-11131 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