ChromeWeb browser · Google
CVE-2016-5148
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 · uneditedCross-site scripting (XSS) vulnerability in Blink, as used in Google Chrome before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92 on Linux, allows remote attackers to inject arbitrary web script or HTML via vectors related to widget updates, aka "Universal XSS (UXSS)."
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 confidenceUniversal XSS (UXSS) vulnerability in Google Chrome's Blink rendering engine (versions before 53.0.2785.89 on Windows/OS X and before 53.0.2785.92 on Linux) allows remote attackers to inject arbitrary web script or HTML via vectors related to widget updates. Unlike regular XSS, this UXSS bypasses same-origin policy restrictions, enabling injection into any website regardless of domain.
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
<= 52.0.2743.116CVSS 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.0/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.
-
Check installed Google Chrome versionOpen Google Chrome, click the menu icon (three dots) in the top right, select Help, then select About Google Chrome. Alternatively, type chrome://version in the address bar or run 'chrome --version' from command line.Affected if The displayed version is 52.0.2743.116 or earlier, or any version below 53.0.2785.89 (Windows/OS X) or below 53.0.2785.92 (Linux)
-
Confirm Chrome uses Blink rendering engineNavigate to chrome://version in the Chrome address bar and check the 'Browser' field or 'User-Agent' string. Google Chrome uses the Blink rendering engine by default.Affected if This is a Chrome-specific vulnerability; other Chromium-based browsers may have different version numbers and patch timelines, but the core check remains the Chrome version itself.
-
Determine operating system platformIdentify whether the Chrome installation runs on Windows, macOS (OS X), or Linux, as the fixed versions differ by platform.Affected if The specific vulnerable threshold depends on OS: Windows/OS X require version 53.0.2785.89 or later, while Linux requires 53.0.2785.92 or later
If the installed Chrome version is 52.0.2743.116 or earlier on any platform, the browser is vulnerable to this UXSS flaw that allows script injection across any origin.
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.
From vendor dataUpdate Google Chrome to version 53.0.2785.89 or later (Windows/OS X) or 53.0.2785.92 or later to patch this vulnerability. Organizations should verify auto-update is enabled or push the update via endpoint management.
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-2016-5148 — 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-2016-5148 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