ChromeWeb browser · Google
CVE-2026-11701
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 · uneditedInappropriate implementation in Guest View in Google Chrome prior to 149.0.7827.103 allowed a remote attacker to perform UI spoofing 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 confidenceA UI spoofing vulnerability in Chrome's Guest View feature allows a remote attacker to craft a malicious HTML page that presents misleading or fake user interface elements, potentially tricking users into believing they're interacting with legitimate content.
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.103CVSS 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
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L
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 installed Chrome versionNavigate to chrome://settings/help or use 'Help > About Google Chrome' in the menu to view the installed version numberAffected if The displayed version is below 149.0.7827.103
-
Confirm Guest View availabilityOpen a new Chrome window and look for the person icon in the top right. If a 'Browse as Guest' option appears in the profile menu or on the Chrome sign-in screen, Guest View is available in this installationAffected if Guest View feature is present and accessible to users
-
Check for Guest Session usageInquire with users or review any enterprise logging/monitoring for Chrome Guest Session launches. Alternatively, check if Chrome is configured to allow Guest profiles via group policy (gpedit.msc > Computer Configuration > Administrative Templates > Google Chrome > Allow Guest Profile)Affected if Users have been using or are permitted to use Guest View sessions in the environment
The environment is affected if the installed Chrome version is below 149.0.7827.103 AND Guest View feature is enabled or accessible to users in the organization.
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.103
Update Google Chrome to version 149.0.7827.103 or later to address this vulnerability.
Chrome 149.0.7827.103 or later (latest stable release)
- 1. Open Google Chrome and navigate to Help > About Google Chrome
- 2. Check the current version number displayed
- 3. If the version is earlier than 149.0.7827.103, Chrome will automatically check for and install updates
- 4. Wait for the update to download and install
- 5. Click 'Relaunch' to restart Chrome and apply the update
- 6. After restart, verify the version is now 149.0.7827.103 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
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11701 — 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-11701 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