Ubuntu vulnerabilities: known CVEs & security history
Canonical · Operating System · 2000 tracked CVEs · 25 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Ubuntu release lines — 2000 in total, with 25 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Ubuntu's current status and the safe version to run.
Known Ubuntu CVEs
Actively-exploited and most-severe first. Showing the top 80 of 2000. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2018-6789⚡ exploited | critical | 9.8 | 82% | 2018 |
| CVE-2016-8735⚡ exploited | critical | 9.8 | 90% | 2017 |
| CVE-2016-3427⚡ exploited | critical | 9.8 | 92% | 2016 |
| CVE-2015-2590⚡ exploited | critical | 9.8 | 26% | 2015 |
| CVE-2014-7169⚡ exploited | critical | 9.8 | 100% | 2014 |
| CVE-2014-6271⚡ exploited | critical | 9.8 | 100% | 2014 |
| CVE-2013-0422⚡ exploited | critical | 9.8 | 98% | 2013 |
| CVE-2011-3544⚡ exploited | critical | 9.8 | 97% | 2011 |
| CVE-2010-4344⚡ exploited | critical | 9.8 | 72% | 2010 |
| CVE-2010-0840⚡ exploited | critical | 9.8 | 96% | 2010 |
| CVE-2016-1646⚡ exploited | high | 8.8 | 45% | 2016 |
| CVE-2015-4495⚡ exploited | high | 8.8 | 70% | 2015 |
| CVE-2013-1690⚡ exploited | high | 8.8 | 69% | 2013 |
| CVE-2016-3714⚡ exploited | high | 8.4 | 97% | 2016 |
| CVE-2017-12617⚡ exploited | high | 8.1 | 100% | 2017 |
| CVE-2014-3153⚡ exploited | high | 7.8 | 37% | 2014 |
| CVE-2010-4345⚡ exploited | high | 7.8 | 18% | 2010 |
| CVE-2010-3904⚡ exploited | high | 7.8 | 11% | 2010 |
| CVE-2014-0160⚡ exploited | high | 7.5 | 100% | 2014 |
| CVE-2016-5195⚡ exploited | high | 7 | 84% | 2016 |
| CVE-2013-1675⚡ exploited | medium | 6.5 | 7% | 2013 |
| CVE-2016-3718⚡ exploited | medium | 5.5 | 77% | 2016 |
| CVE-2016-3715⚡ exploited | medium | 5.5 | 75% | 2016 |
| CVE-2014-0196⚡ exploited | medium | 5.5 | 22% | 2014 |
| CVE-2013-2423⚡ exploited | low | 3.7 | 85% | 2013 |
| CVE-2017-16845 | critical | 10 | 3% | 2017 |
| CVE-2015-8104 | critical | 10 | 3% | 2015 |
| CVE-2017-18206 | critical | 9.8 | 3% | 2018 |
| CVE-2016-10714 | critical | 9.8 | 2% | 2018 |
| CVE-2014-10071 | critical | 9.8 | 3% | 2018 |
| CVE-2018-7225 | critical | 9.8 | 6% | 2018 |
| CVE-2018-7054 | critical | 9.8 | 2% | 2018 |
| CVE-2018-7053 | critical | 9.8 | 2% | 2018 |
| CVE-2018-6871 | critical | 9.8 | 24% | 2018 |
| CVE-2018-1000007 | critical | 9.8 | 8% | 2018 |
| CVE-2017-18017 | critical | 9.8 | 52% | 2018 |
| CVE-2017-17499 | critical | 9.8 | 3% | 2017 |
| CVE-2017-17480 | critical | 9.8 | 5% | 2017 |
| CVE-2017-14746 | critical | 9.8 | 10% | 2017 |
| CVE-2017-16548 | critical | 9.8 | 5% | 2017 |
| CVE-2017-12629 | critical | 9.8 | 92% | 2017 |
| CVE-2017-0903 | critical | 9.8 | 16% | 2017 |
| CVE-2017-15032 | critical | 9.8 | 2% | 2017 |
| CVE-2017-14491 | critical | 9.8 | 85% | 2017 |
| CVE-2017-14493 | critical | 9.8 | 84% | 2017 |
| CVE-2017-14492 | critical | 9.8 | 93% | 2017 |
| CVE-2017-14632 | critical | 9.8 | 6% | 2017 |
| CVE-2017-14626 | critical | 9.8 | 3% | 2017 |
| CVE-2017-14625 | critical | 9.8 | 3% | 2017 |
| CVE-2017-14624 | critical | 9.8 | 3% | 2017 |
| CVE-2017-14532 | critical | 9.8 | 3% | 2017 |
| CVE-2017-14064 | critical | 9.8 | 9% | 2017 |
| CVE-2017-13139 | critical | 9.8 | 4% | 2017 |
| CVE-2017-12762 | critical | 9.8 | 5% | 2017 |
| CVE-2016-9843 | critical | 9.8 | 6% | 2017 |
| CVE-2016-9841 | critical | 9.8 | 7% | 2017 |
| CVE-2017-9058 | critical | 9.8 | 2% | 2017 |
| CVE-2017-5897 | critical | 9.8 | 5% | 2017 |
| CVE-2014-9847 | critical | 9.8 | 4% | 2017 |
| CVE-2014-9846 | critical | 9.8 | 5% | 2017 |
| CVE-2014-9843 | critical | 9.8 | 4% | 2017 |
| CVE-2014-9841 | critical | 9.8 | 4% | 2017 |
| CVE-2015-8768 | critical | 9.8 | 3% | 2017 |
| CVE-2016-2148 | critical | 9.8 | 15% | 2017 |
| CVE-2016-2090 | critical | 9.8 | 3% | 2017 |
| CVE-2016-9013 | critical | 9.8 | 5% | 2016 |
| CVE-2016-7117 | critical | 9.8 | 24% | 2016 |
| CVE-2016-5180 | critical | 9.8 | 9% | 2016 |
| CVE-2016-3955 | critical | 9.8 | 26% | 2016 |
| CVE-2016-5118 | critical | 9.8 | 49% | 2016 |
| CVE-2016-0718 | critical | 9.8 | 13% | 2016 |
| CVE-2016-1580 | critical | 9.8 | 3% | 2016 |
| CVE-2016-1578 | critical | 9.8 | 3% | 2016 |
| CVE-2015-8812 | critical | 9.8 | 14% | 2016 |
| CVE-2016-4002 | critical | 9.8 | 6% | 2016 |
| CVE-2016-3074 | critical | 9.8 | 37% | 2016 |
| CVE-2015-8779 | critical | 9.8 | 6% | 2016 |
| CVE-2015-8778 | critical | 9.8 | 6% | 2016 |
| CVE-2014-9761 | critical | 9.8 | 6% | 2016 |
| CVE-2016-1659 | critical | 9.8 | 1% | 2016 |
1920 older / lower-severity CVEs not shown — see Ubuntu's full record.
Is my Ubuntu version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Ubuntu version → · Monitor Ubuntu for new CVEs →
Ubuntu vulnerabilities — frequently asked
How many known vulnerabilities does Ubuntu have?
IsItPatched tracks 2000 CVEs for Ubuntu, 25 of which are actively exploited (CISA KEV). 103 are critical-severity and 793 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Ubuntu have any actively-exploited vulnerabilities?
Yes — 25 Ubuntu CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild (2 linked to ransomware). Patch these as a priority.
What is the most severe Ubuntu vulnerability?
Among tracked issues, CVE-2018-6789 (CRITICAL, CVSS 9.8), which is actively exploited, ranks highest — a Buffer overflow weakness.
Is Ubuntu safe to use?
It depends on the version. The latest supported Ubuntu release (26.04) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Ubuntu security status · Ubuntu end-of-life · actively-exploited CVEs. Always verify against Canonical's advisories — see our disclaimer.