CVE-2016-10679: selenium-standalone-painful installs a start-selenium command line to start a standalone selenium server with

This month

HIGH 8.1REMOTEUPGRADE

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

selenium-standalone-painful installs a start-selenium command line to start a standalone selenium server with chrome-driver. selenium-standalone-painful 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 ser

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

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

Publisher (CNA): HackerOne · Vendor: selenium-standalone-painful project

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

Am I affected?

Timeline

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

selenium-standalone-painful project selenium-standalone-painful UPGRADE

Affected: <= 2.39.0-2.7.0

Fixed in: newer than 2.39.0-2.7.0

Safe to downgrade to: no unaffected older release

1. Check installed version

npm ls selenium-standalone-painful

2. UPGRADE to newer than 2.39.0-2.7.0

npm install selenium-standalone-painful@">2.39.0-2.7.0"

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-10679?

selenium-standalone-painful: upgrade to newer than 2.39.0-2.7.0. Exact commands for each OS are on this page.

Is CVE-2016-10679 being exploited?

CVE-2016-10679 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-10679 affect?

CVE-2016-10679 affects selenium-standalone-painful. Severity is high (CVSS 8.1). selenium-standalone-painful installs a start-selenium command line to start a standalone selenium server with chrome-driver. selenium-standalone-painful downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It ma

How urgent is CVE-2016-10679?

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

Software pages

Google Chrome vulnerabilities

References

← Back to latest CVEs