CVE-2016-10687 — windows-selenium-chromedr…
HIGHCVE-2016-10687 is a high-severity (CVSS 8.1) CWE-311 vulnerability in windows-selenium-chromedriver. No vendor fix is recorded yet; mitigation options are listed below.
windows-selenium-chromedriver downloads Resources over HTTP
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2016-10687 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
windows-selenium-chromedrivernpmDescription
Affected versions of windows-selenium-chromedriver insecurely download an executable over an unencrypted HTTP connection.
In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running windows-selenium-chromedriver.
Recommendation
No patch is currently available for this vulnerability.
The best mitigation is currently to avoid using this package, using a different package if available.
Alternatively, the risk of exploitation can be reduced by ensuring that this package is not installed while connected to a public network. If the package is installed on a private network, the only people who can exploit this vulnerability are those who have compromised your network or those who have privileged access to your ISP, such as Nation State Actors or Rogue ISP Employees.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | windows-selenium-chromedriver | ≥ 0.0.0 | No fix |
Affected Products
windows-selenium-chromedriverwindows-selenium-chromedriver_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for windows-selenium-chromedriver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of windows-selenium-chromedriver has shipped for CVE-2016-10687 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2016-10687 in your dependencies?
Find it across npm, including transitive dependencies.