louislam
uptime-kuma
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at uptime-kuma, but registry activity is not a publisher support boundary.
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-71285 | 5 Aug 2026 | ≤ 2.4.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-33130 | 20 Mar 2026 | >= 1.23.0, < 2.2.1 | 2.2.1. | Update reference ↗ |
| CVE-2026-32230 | 12 Mar 2026 | >= 2.0.0, < 2.2.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-2024-56331 | 20 Dec 2024 | >= 1.23.0, < 1.23.16; = 2.0.0-beta.0 | 1.23.16 | Update reference ↗ |
| CVE-2023-49805 | 11 Dec 2023 | < 1.23.9 | 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-2023-49804 | 11 Dec 2023 | < 1.23.9 | 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-2023-49276 | 1 Dec 2023 | >= 1.20.0, < 1.23.7 | 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-2023-44400 | 9 Oct 2023 | < 1.23.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-2023-36822 | 5 Jul 2023 | < 1.22.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-2023-36821 | 5 Jul 2023 | < 1.22.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-2023-25811 | 21 Feb 2023 | < 1.20.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-25810 | 21 Feb 2023 | < 1.20.0 | 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.