CVE-2016-1675: n/a vulnerability

CVE-2016-1675: Blink, as used in Google Chrome before 51.0.2704.63, allows remote attackers to bypass the Same Origin Poli...

Blink, as used in Google Chrome before 51.0.2704.63, allows remote attackers to bypass the Same Origin Policy by leveraging the mishandling of Document reattachment during destruction, related to FrameLoader.cpp and LocalFrame.cpp.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 5, 2024, 23:02 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2016-1675 is a Google Chrome/Blink flaw that could let a malicious website bypass Same Origin Policy protections in Chrome versions before 51.0.2704.63. That protection normally prevents one site from reading or manipulating another site's data. The main concern is legacy browser exposure, not modern fully patched Chrome. Exposure is most likely limited to endpoints or Linux Chromium/Chrome packages still running builds older than Google Chrome 51.0.2704.63. Organizations with managed browser fleets should treat this as a legacy software inventory issue unless old browsers remain in use. Prioritize remediation where legacy browsers remain in production or privileged user environments. This is an old issue, but Same Origin Policy bypasses affect a core web security boundary, so any remaining exposure should be eliminated rather than accepted. Mitigation focus: Upgrade Google Chrome or Chromium packages to 51.0.2704.63 or later.; Apply relevant vendor security updates from Debian, Ubuntu, Red Hat, openSUSE, or Gentoo.; Remove unsupported legacy browser versions from managed endpoints..

Prepared: Jun 13, 2026, 14:22 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-1675 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Jun 5, 2016, 23:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://codereview.chromium.org/1858833003CVE reference · x_refsource_CONFIRM
https://crbug.com/600182CVE reference · x_refsource_CONFIRM
RHSA-2016:1190CVE reference · vendor-advisory, x_refsource_REDHAT
GLSA-201607-07CVE reference · vendor-advisory, x_refsource_GENTOO

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.