vino vulnerabilities and fixes
Recent CVEs affecting vino, with upgrade or downgrade steps. 1 tracked.
vino has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2019-10-09. Highest priority: CVE-2019-17414 (score 56/100).
- CVE-2019-17414 HIGH 7.5 UPGRADE tinylcy Vino through 2017-12-15 allows remote attackers to cause a denial of service ("vn_get_string error: Re
FAQ
How do I fix vino 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 vino being exploited right now?
None of the tracked vino CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which vino CVE should I patch first?
CVE-2019-17414 currently ranks highest (56/100): tinylcy Vino through 2017-12-15 allows remote attackers to cause a denial of service ("vn_get_string error: Re.