Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY21 SECURITY RECORDS

mailcow

mailcow-dockerized

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-7460 20 May 2026 2026-03b No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-40878 21 Apr 2026 < 2026-03b No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-40875 21 Apr 2026 < 2026-03b No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-40874 21 Apr 2026 < 2026-03b No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-40873 21 Apr 2026 < 2026-03b No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-40872 21 Apr 2026 < 2026-03b No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-40871 21 Apr 2026 < 2026-03b No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-53909 17 Jul 2025 < 2025-07 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-25198 12 Feb 2025 < 2025-01a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-41960 5 Aug 2024 < 2024-07 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-41959 5 Aug 2024 < 2024-07 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-41958 5 Aug 2024 < 2024-07 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-31204 4 Apr 2024 < 2024-04 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-30270 4 Apr 2024 < 2024-04 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-24760 2 Feb 2024 < 2024-01c 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-23824 2 Feb 2024 < 2024-01 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-49077 30 Nov 2023 < 2023-11 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34108 7 Jun 2023 < 2023-05a 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-26490 3 Mar 2023 < 2023-03 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-39258 27 Sep 2022 < 2022-09 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-2022-31138 11 Jul 2022 < 2022-06a 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.