ChromeWeb browser · Google
CVE-2026-14153
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 Glic in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who convinced a user to engage in specific UI gestures to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)
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 Google Chrome's Glic component (versions prior to 150.0.7871.47) allows remote attackers to manipulate the user interface through specific UI gestures on crafted HTML pages, potentially deceiving users about the authenticity of displayed 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
< 150.0.7871.46CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine the installed Google Chrome versionOpen Google Chrome, click the three-dot menu in the top-right corner, select 'Help', then select 'About Google Chrome'. Alternatively, type chrome://settings/help or chrome://version in the address bar and press Enter.Affected if The displayed version number is less than 150.0.7871.46 (for example, 150.0.7871.45 or any earlier version).
-
Note the full version stringOn the About Google Chrome page, note the complete version string displayed (for example: 150.0.7871.45). Ensure you capture all four number groups separated by periods.Affected if The version string begins with 150.0.7871. and the final number is 45 or lower, or the version begins with a number lower than 150.
-
Verify the attack vector conditionThis vulnerability is triggered when a user visits a crafted HTML page that uses specific UI gestures to deceive users. There is no specific browser setting or flag to disable this vulnerability - it is present in the Glic component of affected versions.Affected if You are running a version of Chrome below 150.0.7871.46 and you browse the web, meaning any visit to a malicious page could trigger the UI spoofing.
Your environment is affected if the installed Google Chrome version is any release prior to 150.0.7871.46 (the fixed version is 150.0.7871.47).
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 · scoped150.0.7871.46
Update Google Chrome to version 150.0.7871.47 or later to obtain the patch for this vulnerability.
Chrome 150.0.7871.47 or later (or latest stable release)
- Open Google Chrome
- Navigate to Settings > About Chrome
- Verify the current version number
- If version is below 150.0.7871.47, Chrome will automatically check for and install updates
- Restart Chrome after the update completes
- Verify the version is now 150.0.7871.47 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
- Implementation0.5 h
- Testing0.5 h
- Review / QA0.3 h
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 locallyCheck whether your project pulls in CVE-2026-14153 — 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-14153 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