Gitea vulnerabilities: known CVEs & security history
Gitea · Version control · 52 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Gitea release lines — 52 in total. A CVE here doesn't mean your version is affected — check Gitea's current status and the safe version to run.
Known Gitea CVEs
Actively-exploited and most-severe first. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2022-42968 | critical | 9.8 | 1% | 2022 |
| CVE-2021-45331 | critical | 9.8 | 1% | 2022 |
| CVE-2021-45330 | critical | 9.8 | 1% | 2022 |
| CVE-2021-45327 | critical | 9.8 | 2% | 2022 |
| CVE-2020-28991 | critical | 9.8 | 2% | 2020 |
| CVE-2019-11576 | critical | 9.8 | 2% | 2019 |
| CVE-2018-18926 | critical | 9.8 | 3% | 2018 |
| CVE-2026-20912 | critical | 9.1 | 0% | 2026 |
| CVE-2026-20897 | critical | 9.1 | 0% | 2026 |
| CVE-2026-20750 | critical | 9.1 | 0% | 2026 |
| CVE-2021-45326 | high | 8.8 | 1% | 2022 |
| CVE-2019-11229 | high | 8.8 | 56% | 2019 |
| CVE-2018-15192 | high | 8.6 | 2% | 2018 |
| CVE-2025-68939 | high | 8.2 | 0% | 2025 |
| CVE-2026-20736 | high | 7.5 | 0% | 2026 |
| CVE-2022-30781 | high | 7.5 | 88% | 2022 |
| CVE-2022-27313 | high | 7.5 | 1% | 2022 |
| CVE-2021-45325 | high | 7.5 | 1% | 2022 |
| CVE-2021-3382 | high | 7.5 | 2% | 2021 |
| CVE-2020-13246 | high | 7.5 | 2% | 2020 |
| CVE-2019-10330 | high | 7.5 | 2% | 2019 |
| CVE-2019-11228 | high | 7.5 | 1% | 2019 |
| CVE-2020-14144 | high | 7.2 | 94% | 2020 |
| CVE-2022-0905 | high | 7.1 | 1% | 2022 |
| CVE-2026-20904 | medium | 6.5 | 0% | 2026 |
| CVE-2026-20883 | medium | 6.5 | 0% | 2026 |
| CVE-2026-20800 | medium | 6.5 | 0% | 2026 |
| CVE-2022-38795 | medium | 6.5 | 0% | 2023 |
| CVE-2022-38183 | medium | 6.5 | 1% | 2022 |
| CVE-2019-1000002 | medium | 6.5 | 1% | 2019 |
| CVE-2022-1058 | medium | 6.1 | 53% | 2022 |
| CVE-2021-45329 | medium | 6.1 | 1% | 2022 |
| CVE-2021-45328 | medium | 6.1 | 1% | 2022 |
| CVE-2019-1010261 | medium | 6.1 | 1% | 2019 |
| CVE-2019-1010314 | medium | 6.1 | 1% | 2019 |
| CVE-2025-68945 | medium | 5.8 | 0% | 2025 |
| CVE-2025-68946 | medium | 5.4 | 0% | 2025 |
| CVE-2025-68942 | medium | 5.4 | 0% | 2025 |
| CVE-2022-1928 | medium | 5.4 | 1% | 2022 |
| CVE-2025-69413 | medium | 5.3 | 0% | 2026 |
| CVE-2025-68943 | medium | 5.3 | 0% | 2025 |
| CVE-2021-29134 | medium | 5.3 | 1% | 2022 |
| CVE-2018-1000803 | medium | 5.3 | 1% | 2018 |
| CVE-2025-68944 | medium | 5 | 0% | 2025 |
| CVE-2025-68941 | medium | 4.9 | 0% | 2025 |
| CVE-2023-3515 | medium | 4.4 | 0% | 2023 |
| CVE-2026-20888 | medium | 4.3 | 0% | 2026 |
| CVE-2025-68938 | medium | 4.3 | 0% | 2025 |
| CVE-2022-46685 | medium | 4.3 | 0% | 2022 |
| CVE-2021-28378 | low | 3.7 | 9% | 2021 |
| CVE-2026-0798 | low | 3.5 | 0% | 2026 |
| CVE-2025-68940 | low | 3.1 | 0% | 2025 |
Is my Gitea 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 Gitea version → · Monitor Gitea for new CVEs →
Gitea vulnerabilities — frequently asked
How many known vulnerabilities does Gitea have?
IsItPatched tracks 52 CVEs for Gitea. 10 are critical-severity and 14 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Gitea have any actively-exploited vulnerabilities?
None of Gitea's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe Gitea vulnerability?
Among tracked issues, CVE-2022-42968 (CRITICAL, CVSS 9.8) ranks highest — a CWE-88 weakness.
Is Gitea safe to use?
It depends on the version. The latest supported Gitea release 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: Gitea security status · Gitea end-of-life · actively-exploited CVEs. Always verify against Gitea's advisories — see our disclaimer.