ChromeWeb browser · Google
CVE-2016-1629
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 · uneditedGoogle Chrome before 48.0.2564.116 allows remote attackers to bypass the Blink Same Origin Policy and a sandbox protection mechanism via unspecified vectors.
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 confidenceGoogle Chrome before version 48.0.2564.116 contains a vulnerability that allows remote attackers to bypass the Blink Same Origin Policy (SOP) and the Chrome sandbox protection mechanism. This enables attackers to potentially execute malicious code or access sensitive data across different origins, circumventing fundamental browser security boundaries.
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
<= 48.0.2564.109
Debian LinuxOperating system
= 8.0= 12= 42.1= 13.1= 13.2CVSS 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.0/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 versionNavigate to chrome://version in the browser address bar, or run 'google-chrome --version' or 'chromium --version' in the terminalAffected if The displayed version number is 48.0.2564.109 or earlier (any version <= 48.0.2564.109)
-
Verify Chrome update statusNavigate to chrome://settings/help or click Help > About Google Chrome to view the update status and current versionAffected if The browser shows an available update or indicates it is running a version before 48.0.2564.116
-
Check Chrome package on Linux systemsOn Debian/Ubuntu run 'dpkg -l | grep chrome'; on RHEL/Fedora run 'rpm -qa | grep chrome'; on SUSE/openSUSE run 'rpm -qa | grep -i chromium'Affected if The installed Chrome package version is 48.0.2564.109-1 or earlier
You are affected if Google Chrome is installed and its version is 48.0.2564.109 or earlier, as versions before 48.0.2564.116 contain the SOP and sandbox bypass vulnerability.
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 · scopedUpgrade Google Chrome to version 48.0.2564.116 or later to remediate this vulnerability. Organizations should prioritize patching browser endpoints given the critical severity and the bypass of both SOP and sandbox protections.
Chrome 48.0.2564.116 or later (or the equivalent patched Chromium package for Linux distributions)
- Update Google Chrome to version 48.0.2564.116 or later
- For Debian 8.0: Run 'apt-get update && apt-get upgrade' or 'apt-get install chromium-browser' to get the updated package
- For Suse Linux Enterprise 12, Leap 42.1, and OpenSUSE 13.1/13.2: Run 'zypper update' or 'zypper in chromium' to obtain the patched Chromium/Chrome package
- Verify the installed version by navigating to chrome://settings/help to confirm the update was successful
- Restart the browser after updating
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1629 — 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-1629 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