NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

CVE-2016-10579 — chromedriver

HIGHFix: giggio/node-chromedriver@7198109

CVE-2016-10579 is a high-severity (CVSS 8.1) CWE-311 vulnerability in chromedriver. A fix is available for chromedriver — see the affected versions and patch details below.

chromedriver Downloads Resources over HTTP

Also known asGHSA-jh5w-6964-x5cf
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk
0.26%0.71%1.16%1.61%0.8%0.8%1.1%1.1%Apr 26Jul 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

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.

457other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
chromedrivernpm
857Kdownloads / week

Description

Chromedriver is an NPM wrapper for selenium ChromeDriver. Chromedriver before 2.26.1 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 binary with an attacker controlled binary if the attacker is on the network or positioned in between the user and the remote server.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmchromedriverall versions2.25.2npm install chromedriver@2.25.2

Affected Products

1 product · 1 configurations
Application
chromedriverchromedriver_project
< 2.26.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for chromedriver, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update chromedriver to 2.25.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2016-10579 is resolved across your whole dependency graph.

  3. Workarounds

    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

Chromedriver is an NPM wrapper for selenium ChromeDriver. Chromedriver before 2.26.1 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 binary with an attacker controlled binary if the attacker is on the network or positioned in between the user and the remote server.
O3 Security · Impact-Aware SCA

Is CVE-2016-10579 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2016-10579: chromedriver RCE — Fixed in 2.25.2