ChromeWeb browser · Google
CVE-2026-11207
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 validation of untrusted input in Autofill in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to potentially perform a sandbox escape via malicious network traffic. (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 confidenceInsufficient validation of untrusted input in Chrome's Autofill feature prior to version 149.0.7827.53 allows remote attackers to potentially escape the sandbox via malicious network traffic. This is an input validation flaw in the Autofill component that could be exploited through specially crafted network responses.
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.
-
Check installed Chrome versionNavigate to chrome://version or click Menu > Help > About Google Chrome. Locate the version number displayed.Affected if The installed version is less than 149.0.7827.53 (e.g., 149.0.7827.52 or earlier)
-
Confirm Autofill is enabledNavigate to chrome://settings/autofill or go to Settings > Autofill and passwords. Verify if any Autofill services are turned on.Affected if Any Autofill feature (addresses, payment methods, passwords, or general Autofill) is enabled in the browser settings
-
Check Chrome channel and update statusNavigate to chrome://settings/help. Observe the channel listed (Stable, Beta, Dev, Canary) and whether an update is available.Affected if The browser is on Beta, Dev, or Canary channel with a version below 149.0.7827.53, or the Stable channel shows an update is available
-
Verify Chrome build dateNavigate to chrome://version and note the OS version and build timestamp. Compare against the release date of version 149.0.7827.53.Affected if The Chrome build was released before the 149.0.7827.53 security update
You are affected if Chrome version is below 149.0.7827.53 AND the Autofill feature is enabled in the browser settings.
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 remediate this vulnerability. Organizations should deploy browser updates via their patch management infrastructure.
Chrome 149.0.7827.53 or later
- Check the current Chrome version by navigating to Settings > About Google Chrome
- If the installed version is less than 149.0.7827.53, click 'Update Google Chrome' to receive the patched version
- Restart Chrome after the update completes
- Verify the update was successful by checking the version again (should be 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
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11207 — 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-11207 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