Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

selenium-standalone-painful vulnerabilities and fixes

Recent CVEs affecting selenium-standalone-painful, with upgrade or downgrade steps. 1 tracked.

Also searched as: selenium standalone painful.

selenium-standalone-painful has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2018-05-29. Highest priority: CVE-2016-10679 (score 54/100).

FAQ

How do I fix selenium-standalone-painful vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is selenium-standalone-painful being exploited right now?

None of the tracked selenium-standalone-painful CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which selenium-standalone-painful CVE should I patch first?

CVE-2016-10679 currently ranks highest (54/100): selenium-standalone-painful installs a start-selenium command line to start a standalone selenium server with .

← Back to latest CVEs