ChromeWeb browser · Google
CVE-2026-0907
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 · uneditedIncorrect security UI in Split View in Google Chrome prior to 144.0.7559.59 allowed a remote attacker 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 · moderate confidenceThis is a UI spoofing vulnerability in Google Chrome's Split View feature that allows a remote attacker to manipulate security UI elements (such as address bar, lock icons, or other trust indicators) via a crafted HTML page. This could trick users into believing they are on a legitimate site when they are actually on a malicious one.
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
< 144.0.7559.59< 144.0.7559.60CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 versionOpen Chrome and navigate to chrome://version, or click Menu > Help > About Google Chrome. The version number is displayed at the top.Affected if The displayed version is lower than 144.0.7559.59 or 144.0.7559.60 (the specific patch version depends on your channel)
-
Identify Chrome release channelIn chrome://version, look for the 'Channels' line or check if you are on Stable, Beta, Dev, or Canary channel. Different channels received different patch versions.Affected if You are on Stable channel and version < 144.0.7559.59, or on Beta/Dev/Canary and version < 144.0.7559.60
-
Verify Split View feature usageSplit View (also called Tab Groups or Window Arrangement) is enabled by right-clicking a tab and selecting 'Move to new window' to create side-by-side windows, or by using the feature that allows two applications to share screen space in the OS.Affected if You actively use Chrome's Split View or tab arrangement features to view windows side-by-side, as this is the feature where the UI spoofing occurs
You are affected if your Chrome version is below 144.0.7559.59 (Stable) or 144.0.7559.60 (Beta/Dev/Canary) AND you use or could be tricked into using the Split View feature with untrusted content.
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 · scoped144.0.7559.59144.0.7559.60
Update Google Chrome to version 144.0.7559.59 or later to remediate this vulnerability. Organizations should ensure automatic updates are enabled or push the update through their patch management systems.
Chrome version 144.0.7559.59 or later
- Open Google Chrome
- Navigate to Chrome Menu > Help > About Google Chrome
- Wait for Chrome to check for updates
- If update is available, click 'Update Google Chrome'
- Restart Chrome browser
- Verify the version by going to chrome://settings/help and confirm version is 144.0.7559.59 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
- 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-0907 — 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-0907 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