Debian vulnerabilities: known CVEs & security history
Debian · Operating System · 1128 tracked CVEs · 22 actively exploited · updated October 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Debian release lines — 1128 in total, with 22 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Debian's current status and the safe version to run.
Known Debian CVEs
Actively-exploited and most-severe first. Showing the top 80 of 1128. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2021-44228⚡ exploited | critical | 10 | 100% | 2021 |
| CVE-2015-3306⚡ exploited | critical | 10 | 98% | 2015 |
| CVE-2026-24061⚡ exploited | critical | 9.8 | 99% | 2026 |
| CVE-2025-39682⚡ exploited | critical | 9.8 | 3% | 2025 |
| CVE-2024-9680⚡ exploited | critical | 9.8 | 23% | 2024 |
| CVE-2020-1938⚡ exploited | critical | 9.8 | 99% | 2020 |
| CVE-2018-7602⚡ exploited | critical | 9.8 | 99% | 2018 |
| CVE-2016-8735⚡ exploited | critical | 9.8 | 90% | 2017 |
| CVE-2012-0507⚡ exploited | critical | 9.8 | 98% | 2012 |
| CVE-2021-40438⚡ exploited | critical | 9 | 100% | 2021 |
| CVE-2025-6558⚡ exploited | high | 8.8 | 10% | 2025 |
| CVE-2023-3079⚡ exploited | high | 8.8 | 32% | 2023 |
| CVE-2017-12617⚡ exploited | high | 8.1 | 100% | 2017 |
| CVE-2025-48384⚡ exploited | high | 8 | 4% | 2025 |
| CVE-2026-31431⚡ exploited | high | 7.8 | 100% | 2026 |
| CVE-2025-38352⚡ exploited | high | 7.8 | 1% | 2025 |
| CVE-2024-1086⚡ exploited | high | 7.8 | 28% | 2024 |
| CVE-2023-4911⚡ exploited | high | 7.8 | 64% | 2023 |
| CVE-2023-44487⚡ exploited | high | 7.5 | 100% | 2023 |
| CVE-2022-30333⚡ exploited | high | 7.5 | 99% | 2022 |
| CVE-2015-5477⚡ exploited | high | 7.5 | 92% | 2015 |
| CVE-2024-50302⚡ exploited | medium | 5.5 | 1% | 2024 |
| CVE-2018-14721 | critical | 10 | 10% | 2019 |
| CVE-2025-39880 | critical | 9.8 | 0% | 2025 |
| CVE-2025-39841 | critical | 9.8 | 0% | 2025 |
| CVE-2025-39703 | critical | 9.8 | 0% | 2025 |
| CVE-2025-39702 | critical | 9.8 | 0% | 2025 |
| CVE-2025-39673 | critical | 9.8 | 0% | 2025 |
| CVE-2025-38724 | critical | 9.8 | 0% | 2025 |
| CVE-2025-38708 | critical | 9.8 | 0% | 2025 |
| CVE-2024-58240 | critical | 9.8 | 0% | 2025 |
| CVE-2025-38561 | critical | 9.8 | 0% | 2025 |
| CVE-2025-38527 | critical | 9.8 | 0% | 2025 |
| CVE-2025-38488 | critical | 9.8 | 0% | 2025 |
| CVE-2025-38476 | critical | 9.8 | 0% | 2025 |
| CVE-2025-38472 | critical | 9.8 | 0% | 2025 |
| CVE-2025-38471 | critical | 9.8 | 0% | 2025 |
| CVE-2025-38439 | critical | 9.8 | 1% | 2025 |
| CVE-2025-38430 | critical | 9.8 | 1% | 2025 |
| CVE-2025-38211 | critical | 9.8 | 0% | 2025 |
| CVE-2025-38075 | critical | 9.8 | 0% | 2025 |
| CVE-2025-37924 | critical | 9.8 | 21% | 2025 |
| CVE-2025-37879 | critical | 9.8 | 0% | 2025 |
| CVE-2025-37778 | critical | 9.8 | 1% | 2025 |
| CVE-2024-52533 | critical | 9.8 | 1% | 2024 |
| CVE-2024-41073 | critical | 9.8 | 0% | 2024 |
| CVE-2024-36886 | critical | 9.8 | 1% | 2024 |
| CVE-2024-35884 | critical | 9.8 | 1% | 2024 |
| CVE-2024-27388 | critical | 9.8 | 0% | 2024 |
| CVE-2024-26877 | critical | 9.8 | 1% | 2024 |
| CVE-2023-51714 | critical | 9.8 | 1% | 2023 |
| CVE-2023-46850 | critical | 9.8 | 2% | 2023 |
| CVE-2022-48174 | critical | 9.8 | 3% | 2023 |
| CVE-2022-32221 | critical | 9.8 | 5% | 2022 |
| CVE-2022-36227 | critical | 9.8 | 2% | 2022 |
| CVE-2022-37454 | critical | 9.8 | 6% | 2022 |
| CVE-2022-37434 | critical | 9.8 | 19% | 2022 |
| CVE-2022-32207 | critical | 9.8 | 8% | 2022 |
| CVE-2022-29155 | critical | 9.8 | 64% | 2022 |
| CVE-2022-25315 | critical | 9.8 | 5% | 2022 |
| CVE-2022-25236 | critical | 9.8 | 34% | 2022 |
| CVE-2022-25235 | critical | 9.8 | 5% | 2022 |
| CVE-2022-23852 | critical | 9.8 | 5% | 2022 |
| CVE-2022-23219 | critical | 9.8 | 4% | 2022 |
| CVE-2022-23218 | critical | 9.8 | 5% | 2022 |
| CVE-2022-22824 | critical | 9.8 | 3% | 2022 |
| CVE-2022-22823 | critical | 9.8 | 3% | 2022 |
| CVE-2022-22822 | critical | 9.8 | 5% | 2022 |
| CVE-2021-3711 | critical | 9.8 | 88% | 2021 |
| CVE-2021-33574 | critical | 9.8 | 3% | 2021 |
| CVE-2021-3177 | critical | 9.8 | 23% | 2021 |
| CVE-2020-6072 | critical | 9.8 | 4% | 2020 |
| CVE-2020-9548 | critical | 9.8 | 19% | 2020 |
| CVE-2020-9547 | critical | 9.8 | 18% | 2020 |
| CVE-2020-9546 | critical | 9.8 | 5% | 2020 |
| CVE-2020-8840 | critical | 9.8 | 27% | 2020 |
| CVE-2019-20330 | critical | 9.8 | 9% | 2020 |
| CVE-2019-17531 | critical | 9.8 | 5% | 2019 |
| CVE-2019-17267 | critical | 9.8 | 5% | 2019 |
| CVE-2019-16943 | critical | 9.8 | 5% | 2019 |
1048 older / lower-severity CVEs not shown — see Debian's full record.
Is my Debian 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 Debian version → · Monitor Debian for new CVEs →
Debian vulnerabilities — frequently asked
How many known vulnerabilities does Debian have?
IsItPatched tracks 1128 CVEs for Debian, 22 of which are actively exploited (CISA KEV). 119 are critical-severity and 683 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Debian have any actively-exploited vulnerabilities?
Yes — 22 Debian CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild (7 linked to ransomware). Patch these as a priority.
What is the most severe Debian vulnerability?
Among tracked issues, CVE-2021-44228 (CRITICAL, CVSS 10), which is actively exploited, ranks highest — a Improper input validation weakness.
Is Debian safe to use?
It depends on the version. The latest supported Debian release (13.7) 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: Debian security status · Debian end-of-life · actively-exploited CVEs. Always verify against Debian's advisories — see our disclaimer.