ChromeWeb browser · Google
CVE-2025-5067
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 Tab Strip in Google Chrome prior to 137.0.7151.55 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 · high confidenceUI spoofing vulnerability in Google Chrome's Tab Strip component prior to version 137.0.7151.55 allows remote attackers to manipulate the tab strip UI through crafted HTML pages, potentially deceiving users about the actual page they're viewing.
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
< 137.0.7151.55CVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Locate your Chrome version numberOpen Google Chrome, click the three-dot menu (top right), select Help, then select About Google Chrome. The version number is displayed on that page.Affected if Unable to retrieve version information
-
Compare your version to the fixNote your installed version number (e.g., 137.0.7151.40) and compare it numerically to 137.0.7151.55. The first three numbers (137.0.7151) are the major version; if they match, compare the final number after the last dot.Affected if Your version is any build earlier than 137.0.7151.55 (e.g., 137.0.7151.40, 136.0.7151.55, or any 136.x/135.x release)
-
Verify the Tab Strip is in useThis vulnerability affects the Tab Strip component which is the standard tab bar at the top of the Chrome window. This is enabled by default in standard Chrome installations - no special configuration needs to be checked.Affected if Using Chrome with the standard tab interface (default configuration)
You are affected if your installed Chrome version is lower than 137.0.7151.55 and you use the standard Tab Strip UI (the default tab bar in Chrome).
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 · scoped137.0.7151.55
Update Google Chrome to version 137.0.7151.55 or later to remediate this vulnerability.
Chrome 137.0.7151.55 or later
- Open Google Chrome browser
- Navigate to Settings > Help > About Google Chrome
- Chrome will automatically check for updates and download version 137.0.7151.55 or later
- Restart the browser to apply 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
- 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-2025-5067 — 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-2025-5067 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