← Search results
CVE-LINKED INVENTORY18 SECURITY RECORDS
squid-cache
squid
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 Squid. 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-47729 | 16 Jul 2026 | < 7.6 | 7.6. | Update reference ↗ |
| CVE-2026-50012 | 16 Jul 2026 | < 7.6 | 7.6. | Update reference ↗ |
| CVE-2026-33526 | 26 Mar 2026 | < 7.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-33515 | 26 Mar 2026 | < 7.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-32748 | 26 Mar 2026 | < 7.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-62168 | 17 Oct 2025 | < 7.2 | 7.2. | Update reference ↗ |
| CVE-2025-54574 | 1 Aug 2025 | < 6.4 | 6.4. | Update reference ↗ |
| CVE-2024-45802 | 28 Oct 2024 | >= 3.0, < 6.10 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-37894 | 25 Jun 2024 | >= 3.0, <= 3.5.28; >= 4.0, <= 4.16; >= 5.0, <= 5.9; >= 6.0, <= 6.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-25111 | 6 Mar 2024 | >= 3.5.27, < 6.8 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the squid service will be restarted automatically. | Update reference ↗ |
| CVE-2024-25617 | 14 Feb 2024 | < 6.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-23638 | 23 Jan 2024 | < 6.6 | 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-50269 | 14 Dec 2023 | >= 2.6, <= 2.7.STABLE9; >= 3.1, <= 5.9; >= 6.0.1, < 6.6 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-49285 | 4 Dec 2023 | >= 2.2, < 6.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-2023-49286 | 4 Dec 2023 | < 6.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-2023-49288 | 4 Dec 2023 | >= 3.5, < 6.0.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-46728 | 6 Nov 2023 | < 6.0.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-46724 | 1 Nov 2023 | >= 3.3.0.1, < 6.4 | 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.