← Search results
CVE-LINKED INVENTORY44 SECURITY RECORDS
Gitea
Gitea
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Gitea. Use that record for publisher support phases and retirement dates.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-97626 | 6 Oct 2026 | Gitea: ≤ 28.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-96594 | 6 Oct 2026 | Gitea: ≤ 28.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-89182 | 6 Oct 2026 | Gitea: 1.27.0 ≤ 28.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-105268 | 6 Oct 2026 | Gitea: ≤ 28.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-105267 | 6 Oct 2026 | Gitea: ≤ 28.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-104633 | 6 Oct 2026 | Gitea: ≤ 28.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-101023 | 6 Oct 2026 | Gitea: ≤ 28.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-97208 | 6 Oct 2026 | Gitea: ≤ 28.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-86684 | 6 Oct 2026 | Gitea: 1.18.0 ≤ 28.0.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-73278 | 6 Oct 2026 | Gitea: 1.16.0 ≤ 1.27.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-96589 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-96580 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-96404 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-96400 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-96399 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-95112 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-94205 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-79960 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-70357 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-104636 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-103504 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-95106 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-89430 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-103670 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-103667 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-101029 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-101027 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-104626 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-103059 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-104632 | 6 Oct 2026 | Gitea: ≤ 1.27.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-60004 | 26 Aug 2026 | Gitea: 1.17 < 1.27.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-34966 | 5 Aug 2026 | Gitea: ≤ 1.26.4 | Gitea: 1.27.0 | Update reference ↗ |
| CVE-2025-69413 | 1 Jan 2026 | < 1.25.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-68946 | 26 Dec 2025 | 1.20.0 < 1.20.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-68945 | 26 Dec 2025 | < 1.21.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-68944 | 26 Dec 2025 | < 1.22.2 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-68943 | 26 Dec 2025 | < 1.21.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-68942 | 26 Dec 2025 | < 1.22.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-68941 | 26 Dec 2025 | < 1.22.3 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-68940 | 26 Dec 2025 | < 1.22.5 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-68939 | 26 Dec 2025 | < 1.23.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-68938 | 26 Dec 2025 | < 1.25.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2019-1010261 | 18 Jul 2019 | 1.7.0 and earlier [fixed: 1.7.1 and later] | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2019-1010314 | 11 Jul 2019 | 1.7.2, 1.7.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.