Downloads Resources over HTTP in selenium-standalone-painful
CVE-2016-10679GHSA-3x83-p476-vv95
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm selenium-standalone-painful
- Affected
- >= 2.39.0-2.7.0, <= 2.39.0-2.7.0
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-3x83-p476-vv95 lists affected ranges: npm selenium-standalone-painful >=2.39.0-2.7.0 <=2.39.0-2.7.0
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-3x83-p476-vv95 lists affected ranges: npm selenium-standalone-painful >=2.39.0-2.7.0 <=2.39.0-2.7.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- CVE-2016-10679: 1.99% estimated exploitation activity in the next 30 days; percentile 80.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Affected versions of selenium-standalone-painful 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 selenium-standalone-painful. 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.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-3x83-p476-vv95
- Revision 1 · created ·
Published from osv record GHSA-3x83-p476-vv95
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2016-10679 Advisory: Downloads Resources over HTTP in selenium-standalone-painful IDs: CVE-2016-10679, GHSA-3x83-p476-vv95 Record: https://patchnext.com/advisories/cve-2016-10679 (revision 2, source checked 26 Oct 2026, 12:07 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm selenium-standalone-painful: affected >= 2.39.0-2.7.0, <= 2.39.0-2.7.0 ## Suggested inspection (read-only) - `npm ls selenium-standalone-painful --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on selenium-standalone-painful. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-3x83-p476-vv95 (OSV record GHSA-3x83-p476-vv95 lists affected ranges: npm selenium-standalone-painful >=2.39.0-2.7.0 <=2.39.0-2.7.0) - Verified: https://github.com/advisories/GHSA-3x83-p476-vv95 (GitHub-reviewed advisory GHSA-3x83-p476-vv95 lists affected ranges: npm selenium-standalone-painful >=2.39.0-2.7.0 <=2.39.0-2.7.0) Commands are suggestions: review each one before running it.
Loading voting…