CVE-2016-1661: n/a vulnerability

CVE-2016-1661: Blink, as used in Google Chrome before 50.0.2661.94, does not ensure that frames satisfy a check for the sa...

Blink, as used in Google Chrome before 50.0.2661.94, does not ensure that frames satisfy a check for the same renderer process in addition to a Same Origin Policy check, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted web site, related to BindingSecurity.cpp and DOMWindow.cpp.

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

Security readout for executives and security teams

CVE-2016-1661 is an old Google Chrome Blink flaw fixed before Chrome 50.0.2661.94. A malicious website could trigger memory corruption, causing a browser crash and possibly other unspecified effects. The main business risk is legacy or unmanaged browser installations that missed 2016 vendor updates. Exposure is most likely in systems still running Google Chrome before 50.0.2661.94 or older distribution-packaged Chromium/Chrome builds covered by 2016 advisories. Modern managed browser fleets are unlikely to remain exposed if normal updates are enforced. Low immediate urgency for modern fleets, but investigate any legacy, frozen, kiosk, or unmanaged browser environments. The vulnerability is remotely reachable through web browsing, yet the sources do not show active exploitation and fixes have existed since 2016. Mitigation focus: Upgrade Chrome or Chromium packages to versions containing the 2016 vendor fixes.; Verify endpoints are not running Chrome before 50.0.2661.94.; Apply relevant Linux distribution security updates for packaged browser builds..

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-1661 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: May 14, 2016, 21: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

4Source 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/1887553002/CVE reference · x_refsource_CONFIRM
https://crbug.com/601629CVE reference · x_refsource_CONFIRM
GLSA-201605-02CVE 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.