CVE-2016-5145

What it is

Blink, as used in Google Chrome before 52.0.2743.116, does not ensure that a taint property is preserved after a structure-clone operation on an ImageBitmap object derived from a cross-origin image, which allows remote attackers to bypass the Same Origin Policy via crafted JavaScript code.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.

Exploit odds

1.3% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2016-08-07 19:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:48 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.3% in the next 30 days (EPSS).
• Severity: 8.8 HIGH (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2016-08-07 19:59 UTC

Last modified

2026-06-17 00:48 UTC

Exploit probability

1.3% · EPSS, next 30 days

Weakness

CWE-254

Record status

Modified

Affected

• Google Chrome ≤ 52.0.2743.82

Attack profile CVSS 3.0 · 8.8

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2016-5145.md and follow it. Check whether this project is affected by CVE-2016-5145. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge