← Search results
CVE-LINKED INVENTORY23 SECURITY RECORDS
0xJacky
nginx-ui
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 nginx-ui, 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-44015 | 12 May 2026 | <= 2.3.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-42238 | 4 May 2026 | < 2.3.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-42223 | 4 May 2026 | < 2.3.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-42222 | 4 May 2026 | = 2.3.5 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-42221 | 4 May 2026 | >= 2.0.0, < 2.3.8 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-42220 | 4 May 2026 | < 2.3.8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-34403 | 20 Apr 2026 | < 2.3.5 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-33031 | 20 Apr 2026 | < 2.3.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-33026 | 30 Mar 2026 | < 2.3.4 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-33027 | 30 Mar 2026 | < 2.3.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-33028 | 30 Mar 2026 | < 2.3.4 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-33029 | 30 Mar 2026 | < 2.3.4 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-33030 | 30 Mar 2026 | <= 2.3.3 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-33032 | 30 Mar 2026 | <= 2.3.5 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-27944 | 5 Mar 2026 | < 2.3.3 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-49368 | 21 Oct 2024 | < 2.0.0-beta.36 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-49367 | 21 Oct 2024 | < 2.0.0-beta.36 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-49366 | 21 Oct 2024 | < 2.0.0-beta.36 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-23828 | 29 Jan 2024 | < v2.0.0.beta.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-23827 | 29 Jan 2024 | < 2.0.0.beta.12 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-22198 | 11 Jan 2024 | < 2.0.0.beta.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-2024-22196 | 11 Jan 2024 | < 2.0.0.beta.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-2024-22197 | 11 Jan 2024 | < 2.0.0.beta.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 ↗ |
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.