CVE-2016-1693

What it is

browser/safe_browsing/srt_field_trial_win.cc in Google Chrome before 51.0.2704.63 does not use the HTTPS service on dl.google.com to obtain the Software Removal Tool, which allows remote attackers to spoof the chrome_cleanup_tool.exe (aka CCT) file via a man-in-the-middle attack on an HTTP session.

At a glance

Exploitability

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

Exploit odds

1.2% 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-06-05 23:59 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 00:42 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.2% in the next 30 days (EPSS).
• Severity: 5.3 MEDIUM (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2016-06-05 23:59 UTC

Last modified

2026-06-17 00:42 UTC

Exploit probability

1.2% · EPSS, next 30 days

Weakness

CWE-284 · Improper access control

Record status

Modified

Affected

• Debian Linux 8.0
• Opensuse Leap 42.1
• Opensuse 13.2
• Redhat Enterprise Linux Desktop 6.0
• Redhat Enterprise Linux Server 6.0
• Redhat Enterprise Linux Workstation 6.0
• Suse Linux Enterprise 12.0
• Google Chrome ≤ 50.0.2661.102

Attack profile CVSS 3.0 · 5.3

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

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-1693.md and follow it. Check whether this project is affected by CVE-2016-1693. 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