← Search results
CVE-LINKED INVENTORY20 SECURITY RECORDS
Red Hat
Red Hat Enterprise Linux 7
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 Red Hat Enterprise Linux 7. 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-71224 | 3 Sep 2026 | See the vendor and CVE records for the affected range. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-71222 | 3 Sep 2026 | See the vendor and CVE records for the affected range. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-71221 | 3 Sep 2026 | See the vendor and CVE records for the affected range. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-71220 | 3 Sep 2026 | See the vendor and CVE records for the affected range. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-71219 | 3 Sep 2026 | See the vendor and CVE records for the affected range. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-19411 | 10 Aug 2026 | See the vendor and CVE records for the affected range. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-61028 | 23 Jun 2026 | See the vendor and CVE records for the affected range. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-61023 | 23 Jun 2026 | See the vendor and CVE records for the affected range. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-2239 | 26 Mar 2026 | See the vendor and CVE records for the affected range. | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-40551 | 29 Jan 2024 | See the vendor and CVE records for the affected range. | 0:15.8-3.el7 < *; 0:15.8-1.el7 < *; 0:15.8-4.el8_9 < *; 0:15.8-2.el8_2 < *; 0:15.8-2.el8_4 < * | Update reference ↗ |
| CVE-2023-40546 | 29 Jan 2024 | See the vendor and CVE records for the affected range. | 0:15.8-3.el7 < *; 0:15.8-1.el7 < *; 0:15.8-4.el8_9 < *; 0:15.8-2.el8_2 < *; 0:15.8-2.el8_4 < * | Update reference ↗ |
| CVE-2023-40549 | 29 Jan 2024 | See the vendor and CVE records for the affected range. | 0:15.8-3.el7 < *; 0:15.8-1.el7 < *; 0:15.8-4.el8_9 < *; 0:15.8-2.el8_2 < *; 0:15.8-2.el8_4 < * | Update reference ↗ |
| CVE-2023-40550 | 29 Jan 2024 | See the vendor and CVE records for the affected range. | 0:15.8-3.el7 < *; 0:15.8-1.el7 < *; 0:15.8-4.el8_9 < *; 0:15.8-2.el8_2 < *; 0:15.8-2.el8_4 < * | Update reference ↗ |
| CVE-2023-40548 | 29 Jan 2024 | See the vendor and CVE records for the affected range. | 0:15.8-3.el7 < *; 0:15.8-1.el7 < *; 0:15.8-4.el8_9 < *; 0:15.8-2.el8_2 < *; 0:15.8-2.el8_4 < * | Update reference ↗ |
| CVE-2023-40547 | 25 Jan 2024 | See the vendor and CVE records for the affected range. | 0:15.8-3.el7 < *; 0:15.8-1.el7 < *; 0:15.8-4.el8_9 < *; 0:15.8-2.el8_2 < *; 0:15.8-2.el8_4 < * | Update reference ↗ |
| CVE-2023-5455 | 10 Jan 2024 | See the vendor and CVE records for the affected range. | 0:4.6.8-5.el7_9.16 < *; 8090020231201152514.3387e3d0 < *; 8020020231123154806.792f4060 < *; 8040020231123154610.5b01ab7e < * | Update reference ↗ |
| CVE-2023-3972 | 1 Nov 2023 | See the vendor and CVE records for the affected range. | 0:3.1.9-1.el7_9 < *; 0:3.2.2-1.el8_8 < *; 0:3.2.3-1.el8_1 < *; 0:3.2.3-1.el8_2 < *; 0:3.2.3-1.el8_4 < * | Update reference ↗ |
| CVE-2023-5380 | 25 Oct 2023 | See the vendor and CVE records for the affected range. | 0:1.8.0-26.el7_9 < *; 0:1.20.11-22.el8 < *; 0:1.13.1-8.el8 < *; 0:1.20.11-24.el9 < *; 0:1.13.1-8.el9 < * | Update reference ↗ |
| CVE-2023-42753 | 25 Sep 2023 | See the vendor and CVE records for the affected range. | 0:3.10.0-1160.108.1.rt56.1259.el7 < *; 0:3.10.0-1160.108.1.el7 < *; 0:3.10.0-1062.85.1.el7 < *; 0:4.18.0-513.11.1.rt7.313.el8_9 < *; 0:4.18.0-513.11.1.el8_9 < *; 0:4.18.0-193.120.1.el8_2 < * | Update reference ↗ |
| CVE-2023-3899 | 23 Aug 2023 | See the vendor and CVE records for the affected range. | 0:1.24.52-2.el7_9 < *; 0:1.28.36-3.el8_8 < *; 0:1.25.17.1-2.el8_1 < *; 0:1.26.22-2.el8_2 < *; 0:1.28.13-7.el8_4 < * | 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.