dbcve.org
ChromeWeb browser · Google

CVE-2020-16036

MEDIUM · 6.5 CVSS v3.1 Published 2021-01-08
Fix available
A fix is available. Upgrade to 87.0.4280.66 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Inappropriate implementation in cookies in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to bypass cookie restrictions via a crafted HTML page.

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 confidence

An inappropriate implementation in Chrome's cookie handling allowed a remote attacker to bypass cookie restrictions via a crafted HTML page. This vulnerability in versions prior to 87.0.4280.66 permitted cookie security policy bypass, likely affecting SameSite cookie enforcement or similar cookie access controls.

MitigationUpdate Google Chrome to version 87.0.4280.66 or later to obtain the cookie restriction fix.

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
Affected:< 87.0.4280.66

CVSS 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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Find installed Google Chrome version
    Open Chrome, click the three-dot menu (top right), select Help, then About Google Chrome. The version number is displayed on that page.
    Affected if version shown is less than 87.0.4280.66
  2. Verify version via command line (optional)
    On Windows, open Command Prompt and run: chrome --version or look in the Chrome installation folder for version info. On macOS, run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
    Affected if reported version is less than 87.0.4280.66
  3. Check Chrome's internal version number
    In Chrome address bar, type chrome://version and press Enter. The first line shows the full version including build number.
    Affected if version number before the build is below 87.0.4280.66

You are affected if your installed Google Chrome version is any version earlier than 87.0.4280.66, as earlier versions contain the cookie restriction bypass flaw.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 87.0.4280.66 or later
Fixed in 87.0.4280.66
Interim mitigation

Update Google Chrome to version 87.0.4280.66 or later to obtain the cookie restriction fix.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-16036 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-16036 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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