← Search results
CVE-LINKED INVENTORY34 SECURITY RECORDS
Rack
Rack
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 rack, 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-26962 | 2 Apr 2026 | >= 3.2.0, < 3.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-34835 | 2 Apr 2026 | >= 3.0.0.beta1, < 3.1.21; >= 3.2.0, < 3.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-34827 | 2 Apr 2026 | >= 3.0.0.beta1, < 3.1.21; >= 3.2.0, < 3.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-32762 | 2 Apr 2026 | >= 3.0.0.beta1, < 3.1.21; >= 3.2.0, < 3.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-34830 | 2 Apr 2026 | < 2.2.23; >= 3.0.0.beta1, < 3.1.21; >= 3.2.0, < 3.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-34829 | 2 Apr 2026 | < 2.2.23; >= 3.0.0.beta1, < 3.1.21; >= 3.2.0, < 3.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-34826 | 2 Apr 2026 | < 2.2.23; >= 3.0.0.beta1, < 3.1.21; >= 3.2.0, < 3.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-34786 | 2 Apr 2026 | < 2.2.23; >= 3.0.0.beta1, < 3.1.21; >= 3.2.0, < 3.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-34785 | 2 Apr 2026 | < 2.2.23; >= 3.0.0.beta1, < 3.1.21; >= 3.2.0, < 3.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-34763 | 2 Apr 2026 | < 2.2.23; >= 3.0.0.beta1, < 3.1.21; >= 3.2.0, < 3.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-34831 | 2 Apr 2026 | < 2.2.23; >= 3.0.0.beta1, < 3.1.21; >= 3.2.0, < 3.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-26961 | 2 Apr 2026 | < 2.2.23; >= 3.0.0.beta1, < 3.1.21; >= 3.2.0, < 3.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-34230 | 2 Apr 2026 | < 2.2.23; >= 3.0.0.beta1, < 3.1.21; >= 3.2.0, < 3.2.6 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25500 | 18 Feb 2026 | < 2.2.22; >= 3.0.0.beta1, < 3.1.20; >= 3.2.0, < 3.2.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-2026-22860 | 18 Feb 2026 | < 2.2.22; >= 3.0.0.beta1, < 3.1.20; >= 3.2.0, < 3.2.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-61919 | 10 Oct 2025 | < 2.2.20; >= 3.0, < 3.1.18; >= 3.2, < 3.2.3 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-61780 | 10 Oct 2025 | < 2.2.20; >= 3.0, < 3.1.18; >= 3.2, < 3.2.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-61772 | 7 Oct 2025 | < 2.2.19; >= 3.1, < 3.1.17; >= 3.2, < 3.2.2 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-61771 | 7 Oct 2025 | < 2.2.19; >= 3.1, < 3.1.17; >= 3.2, < 3.2.2 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-61770 | 7 Oct 2025 | < 2.2.19; >= 3.1, < 3.1.17; >= 3.2, < 3.2.2 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-59830 | 25 Sep 2025 | < 2.2.18 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-49007 | 4 Jun 2025 | >= 3.1.0, < 3.1.16 | 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-46727 | 7 May 2025 | < 2.2.14; >= 3.0, < 3.0.16; >= 3.1, < 3.1.14 | 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-32441 | 7 May 2025 | < 2.2.14 | 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-27610 | 10 Mar 2025 | < 2.2.13; >= 3.0, < 3.0.14; >= 3.1, < 3.1.12 | 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-27111 | 4 Mar 2025 | < 2.2.12; >= 3.0, < 3.0.13; >= 3.1, < 3.1.11 | 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-25184 | 12 Feb 2025 | < 2.2.11; >= 3.0, < 3.0.12; >= 3.1, < 3.1.10 | 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-39316 | 2 Jul 2024 | >= 3.1.0, < 3.1.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-2024-26141 | 28 Feb 2024 | >= 3.0.0, < 3.0.9.1; >= 1.3.0, < 2.2.8.1 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.15/html/updating_red_hat_satellite/index | Update reference ↗ |
| CVE-2024-25126 | 28 Feb 2024 | >= 3.0.0, < 3.0.9.1; >= 0.4, < 2.2.8.1 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.15/html/updating_red_hat_satellite/index | Update reference ↗ |
| CVE-2024-26146 | 28 Feb 2024 | >= 3.0.0, < 3.0.9.1; >= 2.2.0, < 2.2.8.1; >= 2.1.0, < 2.1.4.4; < 2.0.9.4 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For detailed instructions how to apply this update, refer to: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.15/html/updating_red_hat_satellite/index | Update reference ↗ |
| CVE-2019-16782 | 18 Dec 2019 | before 1.6.12 or 2.0.8 | 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-2018-16471 | 13 Nov 2018 | 2.0.6, 1.6.11 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-16470 | 13 Nov 2018 | 2.0.6 | 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.