CVE-2016-10696: windows-latestchromedriver downloads the latest version of chromedriver.exe

Q: How do I fix CVE-2016-10696?

windows-latestchromedriver: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2016-10696 being exploited?

CVE-2016-10696 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2016-10696 affect?

CVE-2016-10696 affects windows-latestchromedriver. Severity is high (CVSS 8.1). windows-latestchromedriver downloads the latest version of chromedriver.exe. windows-latestchromedriver downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE

Q: How urgent is CVE-2016-10696?

Priority 53/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 8.1REMOTEDOWNGRADE

CVE-2016-10696 is a high-severity flaw (CVSS 8.1) affecting windows-latestchromedriver. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

windows-latestchromedriver downloads the latest version of chromedriver.exe. windows-latestchromedriver downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested resources with an attacker controlled copy if the attacker is on the network or positioned in between the user and the remote server.

Why this priority

High severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	1.7% (top 23%)
CISA exploited list	No
Weakness	CWE-311, CWE-310
Published	2018-06-04
Last modified	2026-06-17

Publisher (CNA): HackerOne · Vendor: windows-latestchromedriver project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-06-04 19:29 UTCPublished CVE record published
2026-06-17 00:40 UTCUpdated Record last modified

windows-latestchromedriver project windows-latestchromedriver DOWNGRADE

Affected: 0.1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.1.0

1. Check installed version

npm ls windows-latestchromedriver

2. No fixed release: DOWNGRADE to a release before 0.1.0

npm view windows-latestchromedriver versions npm install windows-latestchromedriver@"<0.1.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-10696?

windows-latestchromedriver: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2016-10696 being exploited?

CVE-2016-10696 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-10696 affect?

CVE-2016-10696 affects windows-latestchromedriver. Severity is high (CVSS 8.1). windows-latestchromedriver downloads the latest version of chromedriver.exe. windows-latestchromedriver downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE

How urgent is CVE-2016-10696?

Priority 53/100. High severity; Remotely exploitable, no login, no user action

Software pages

Windows vulnerabilities

References

← Back to latest CVEs