ChromeWeb browser · Google
CVE-2026-14145
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 CSS in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to inject arbitrary scripts or HTML (UXSS) 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 Universal Cross-Site Scripting (UXSS) vulnerability in Google Chrome's CSS implementation prior to version 150.0.7871.47 allows a remote attacker to inject arbitrary scripts or HTML via a crafted HTML page. The inappropriate implementation in CSS parsing enables bypassing same-origin policy protections.
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.47CVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify if Google Chrome is installedCheck for Chrome executable on the system - common paths include C:\Program Files\Google\Chrome\Application\chrome.exe on Windows, /Applications/Google Chrome on macOS, or /opt/google/chrome/google-chrome on Linux. On any OS, you can also run 'google-chrome --version' in a terminal.Affected if Google Chrome is present on the system
-
Retrieve the installed Chrome version numberOpen Google Chrome and navigate to chrome://version in the address bar, or run 'google-chrome --version' from the command line, or right-click the chrome.exe and select Properties to view the version on the Details tab.Affected if Chrome version cannot be determined or retrieved
-
Compare version against the affected rangeParse the full version string from step 2. Extract the version components (e.g., for 150.0.7871.45: major=150, minor=0, build=7871, patch=45). Compare numerically against the affected threshold version 150.0.7871.47.Affected if The installed version is below 150.0.7871.47 (any version starting with 149.x or earlier, or version 150.x with build lower than 7871, or build 7871 with patch lower than 47)
The user is affected if Google Chrome is installed and its version number is less than 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.47
Update Google Chrome to version 150.0.7871.47 or later to remediate this vulnerability. Users should be advised to update their browsers as this is a client-side vulnerability with no server-side mitigation available.
Chrome 150.0.7871.47 or later
- Open Google Chrome browser
- Navigate to Chrome Settings (three-dot menu > Settings)
- Click on 'About Chrome' in the left sidebar
- Chrome will automatically check for updates
- If an update is available, click 'Update Google Chrome'
- Restart the browser to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14145 — 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-14145 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