Fedora vulnerabilities: known CVEs & security history
Fedora Project · OS / Linux · 421 tracked CVEs · 12 actively exploited · updated October 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Fedora release lines — 421 in total, with 12 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Fedora's current status and the safe version to run.
Known Fedora CVEs
Actively-exploited and most-severe first. Showing the top 80 of 421. 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-2020-1938⚡ exploited | critical | 9.8 | 99% | 2020 |
| CVE-2021-40438⚡ exploited | critical | 9 | 100% | 2021 |
| CVE-2023-3079⚡ exploited | high | 8.8 | 32% | 2023 |
| CVE-2022-2294⚡ exploited | high | 8.8 | 70% | 2022 |
| CVE-2024-1086⚡ exploited | high | 7.8 | 28% | 2024 |
| CVE-2023-4911⚡ exploited | high | 7.8 | 64% | 2023 |
| CVE-2022-0995⚡ exploited | high | 7.8 | 6% | 2022 |
| CVE-2023-44487⚡ exploited | high | 7.5 | 100% | 2023 |
| CVE-2023-38180⚡ exploited | high | 7.5 | 15% | 2023 |
| CVE-2015-5477⚡ exploited | high | 7.5 | 92% | 2015 |
| CVE-2023-46850 | critical | 9.8 | 2% | 2023 |
| CVE-2023-38408 | critical | 9.8 | 80% | 2023 |
| 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-32511 | critical | 9.8 | 2% | 2022 |
| CVE-2022-25315 | critical | 9.8 | 5% | 2022 |
| CVE-2022-25235 | critical | 9.8 | 5% | 2022 |
| CVE-2022-23304 | critical | 9.8 | 2% | 2022 |
| CVE-2022-23303 | critical | 9.8 | 3% | 2022 |
| CVE-2021-33574 | critical | 9.8 | 3% | 2021 |
| CVE-2021-20232 | critical | 9.8 | 3% | 2021 |
| CVE-2021-20231 | critical | 9.8 | 4% | 2021 |
| CVE-2021-3177 | critical | 9.8 | 23% | 2021 |
| CVE-2020-27619 | critical | 9.8 | 8% | 2020 |
| CVE-2019-16943 | critical | 9.8 | 5% | 2019 |
| CVE-2019-16942 | critical | 9.8 | 6% | 2019 |
| CVE-2019-5482 | critical | 9.8 | 18% | 2019 |
| CVE-2019-5481 | critical | 9.8 | 7% | 2019 |
| CVE-2019-16335 | critical | 9.8 | 5% | 2019 |
| CVE-2019-14540 | critical | 9.8 | 11% | 2019 |
| CVE-2019-14379 | critical | 9.8 | 8% | 2019 |
| CVE-2019-10160 | critical | 9.8 | 5% | 2019 |
| CVE-2019-8457 | critical | 9.8 | 45% | 2019 |
| CVE-2019-9636 | critical | 9.8 | 8% | 2019 |
| CVE-2021-46848 | critical | 9.1 | 2% | 2022 |
| CVE-2021-33643 | critical | 9.1 | 1% | 2022 |
| CVE-2021-22945 | critical | 9.1 | 7% | 2021 |
| CVE-2019-20445 | critical | 9.1 | 13% | 2020 |
| CVE-2019-20444 | critical | 9.1 | 9% | 2020 |
| CVE-2019-9948 | critical | 9.1 | 12% | 2019 |
| CVE-2019-3859 | critical | 9.1 | 6% | 2019 |
| CVE-2023-6879 | critical | 9 | 1% | 2023 |
| CVE-2026-35093 | high | 8.8 | 0% | 2026 |
| CVE-2023-41074 | high | 8.8 | 4% | 2023 |
| CVE-2023-27534 | high | 8.8 | 2% | 2023 |
| CVE-2023-27533 | high | 8.8 | 2% | 2023 |
| CVE-2022-42719 | high | 8.8 | 1% | 2022 |
| CVE-2022-24407 | high | 8.8 | 4% | 2022 |
| CVE-2021-3518 | high | 8.8 | 22% | 2021 |
| CVE-2020-36327 | high | 8.8 | 6% | 2021 |
| CVE-2020-10531 | high | 8.8 | 3% | 2020 |
| CVE-2019-3857 | high | 8.8 | 6% | 2019 |
| CVE-2019-3856 | high | 8.8 | 6% | 2019 |
| CVE-2019-3855 | high | 8.8 | 9% | 2019 |
| CVE-2024-2398 | high | 8.6 | 36% | 2024 |
| CVE-2024-21626 | high | 8.6 | 18% | 2024 |
| CVE-2021-3517 | high | 8.6 | 17% | 2021 |
| CVE-2020-10878 | high | 8.6 | 5% | 2020 |
| CVE-2021-39152 | high | 8.5 | 11% | 2021 |
| CVE-2021-39150 | high | 8.5 | 3% | 2021 |
| CVE-2021-39154 | high | 8.5 | 5% | 2021 |
| CVE-2021-39153 | high | 8.5 | 4% | 2021 |
| CVE-2021-39151 | high | 8.5 | 5% | 2021 |
| CVE-2021-39149 | high | 8.5 | 5% | 2021 |
| CVE-2021-39148 | high | 8.5 | 5% | 2021 |
| CVE-2021-39147 | high | 8.5 | 5% | 2021 |
| CVE-2021-39146 | high | 8.5 | 14% | 2021 |
| CVE-2021-39145 | high | 8.5 | 4% | 2021 |
| CVE-2021-39141 | high | 8.5 | 16% | 2021 |
| CVE-2021-39139 | high | 8.5 | 5% | 2021 |
| CVE-2024-27018 | high | 8.2 | 0% | 2024 |
| CVE-2021-41164 | high | 8.2 | 1% | 2021 |
| CVE-2020-11987 | high | 8.2 | 13% | 2021 |
| CVE-2020-10543 | high | 8.2 | 11% | 2020 |
| CVE-2024-22373 | high | 8.1 | 1% | 2024 |
| CVE-2022-38023 | high | 8.1 | 2% | 2022 |
341 older / lower-severity CVEs not shown — see Fedora's full record.
Is my Fedora 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 Fedora version → · Monitor Fedora for new CVEs →
Fedora vulnerabilities — frequently asked
How many known vulnerabilities does Fedora have?
IsItPatched tracks 421 CVEs for Fedora, 12 of which are actively exploited (CISA KEV). 38 are critical-severity and 221 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Fedora have any actively-exploited vulnerabilities?
Yes — 12 Fedora CVEs are in CISA's Known Exploited Vulnerabilities catalog, meaning they are confirmed exploited in the wild (4 linked to ransomware). Patch these as a priority.
What is the most severe Fedora vulnerability?
Among tracked issues, CVE-2021-44228 (CRITICAL, CVSS 10), which is actively exploited, ranks highest — a Improper input validation weakness.
Is Fedora safe to use?
It depends on the version. The latest supported Fedora release (44) 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: Fedora security status · Fedora end-of-life · actively-exploited CVEs. Always verify against Fedora Project's advisories — see our disclaimer.