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

GitHub

Enterprise Server

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-75101 22 Sep 2026 Enterprise Server: 3.17.0 < 3.17.*, 3.18.0 < 3.18.*, 3.19.0 < 3.19.*, 3.20.0 < 3.20.*, 3.21.0 < 3.21.* No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-77912 22 Sep 2026 Enterprise Server: 3.17.0 < 3.17.*, 3.18.0 < 3.18.*, 3.19.0 < 3.19.*, 3.20.0 < 3.20.*, 3.21.0 < 3.21.*, 3.22.0 < 3.22.* No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-77987 22 Sep 2026 Enterprise Server: 3.17.0 < 3.17.*, 3.18.0 < 3.18.*, 3.19.0 < 3.19.*, 3.20.0 < 3.20.*, 3.21.0 < 3.21.*, 3.22.0 < 3.22.* No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-76851 1 Sep 2026 3.17.0 ≤ 3.17.19; 3.18.0 ≤ 3.18.13; 3.19.0 ≤ 3.19.10; 3.20.0 ≤ 3.20.6; 3.21.0 ≤ 3.21.4 3.22.0 Update reference ↗
CVE-2026-19118 1 Sep 2026 3.17.0 ≤ 3.17.19; 3.18.0 ≤ 3.18.13; 3.19.0 ≤ 3.19.10; 3.20.0 ≤ 3.20.6; 3.21.0 ≤ 3.21.4 3.22.0 Update reference ↗
CVE-2026-18730 1 Sep 2026 Enterprise Server: 3.17.0 < 3.17.*, 3.18.0 < 3.18.*, 3.19.0 < 3.19.*, 3.20.0 < 3.20.*, 3.21.0 < 3.21.* No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-15996 5 Aug 2026 3.17.0 ≤ 3.17.15; 3.18.0 ≤ 3.18.9; 3.19.0 ≤ 3.19.6; 3.20.0 ≤ 3.20.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-17556 5 Aug 2026 3.17.0 ≤ 3.17.18; 3.18.0 ≤ 3.18.12; 3.19.0 ≤ 3.19.9; 3.20.0 ≤ 3.20.5; 3.21.0 ≤ 3.21.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-15783 17 Jul 2026 3.17.0 ≤ 3.17.17; 3.18.0 ≤ 3.18.11; 3.19.0 ≤ 3.19.8; 3.20.0 ≤ 3.20.4; 3.21.0 ≤ 3.21.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-15343 17 Jul 2026 3.17.0 ≤ 3.17.17; 3.18.0 ≤ 3.18.11; 3.19.0 ≤ 3.19.8; 3.20.0 ≤ 3.20.4; 3.21.0 ≤ 3.21.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-15007 17 Jul 2026 3.17.0 ≤ 3.17.17; 3.18.0 ≤ 3.18.11; 3.19.0 ≤ 3.19.8; 3.20.0 ≤ 3.20.4; 3.21.0 ≤ 3.21.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-14340 1 Jul 2026 3.16.0 ≤ 3.16.19; 3.17.0 ≤ 3.17.16; 3.18.0 ≤ 3.18.10; 3.19.0 ≤ 3.19.7; 3.20.0 ≤ 3.20.3; 3.21.0 ≤ 3.21.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-10585 30 Jun 2026 3.17.0 ≤ 3.17.16; 3.18.0 ≤ 3.18.10; 3.19.0 ≤ 3.19.7; 3.20.0 ≤ 3.20.3; 3.16.0 ≤ 3.16.19 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-9132 30 Jun 2026 3.17.0 ≤ 3.17.16; 3.18.0 ≤ 3.18.10; 3.19.0 ≤ 3.19.7; 3.20.0 ≤ 3.20.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-9106 30 Jun 2026 3.17.0 ≤ 3.17.16; 3.18.0 ≤ 3.18.10; 3.19.0 ≤ 3.19.7; 3.20.0 ≤ 3.20.3; 3.21.0 ≤ 3.21.1; 3.16.0 ≤ 3.16.19 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-9312 27 May 2026 3.16.0 ≤ 3.16.19; 3.17.0 ≤ 3.17.16; 3.18.0 ≤ 3.18.10; 3.19.0 ≤ 3.19.7; 3.20.0 ≤ 3.20.3; 3.21.0 < 3.21.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-8606 26 May 2026 3.21.0 < 3.21.1; 3.20.0 ≤ 3.20.2; 3.19.0 ≤ 3.19.6; 3.18.0 ≤ 3.18.9; 3.17.0 ≤ 3.17.15; 3.16.0 ≤ 3.16.18 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-8106 7 May 2026 3.19.1 ≤ 3.19.5; 3.20.0 ≤ 3.20.1 3.19.0; 3.21.0 Update reference ↗
CVE-2026-8034 7 May 2026 3.16.0 ≤ 3.16.17; 3.17.0 ≤ 3.17.14; 3.18.0 ≤ 3.18.8; 3.19.0 ≤ 3.19.5; 3.20.0 ≤ 3.20.1 3.21.0 Update reference ↗
CVE-2026-7541 7 May 2026 3.16.0 ≤ 3.16.17; 3.17.0 ≤ 3.17.14; 3.18.0 ≤ 3.18.8; 3.19.0 ≤ 3.19.5; 3.20.0 ≤ 3.20.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-6736 7 May 2026 3.16.0 ≤ 3.16.17; 3.17.0 ≤ 3.17.14; 3.18.0 ≤ 3.18.8; 3.19.0 ≤ 3.19.5; 3.20.0 ≤ 3.20.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5845 21 Apr 2026 3.20.0 < 3.20.1; 3.19.0 ≤ 3.19.4; 3.18.0 ≤ 3.18.7; 3.17.0 ≤ 3.17.13; 3.16.0 ≤ 3.16.16; 3.15.0 ≤ 3.15.20; 3.14.0 ≤ 3.14.25 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-3307 21 Apr 2026 3.14.0 ≤ 3.14.24; 3.15.0 ≤ 3.15.19; 3.16.0 ≤ 3.16.15; 3.17.0 ≤ 3.17.12; 3.18.0 ≤ 3.18.6; 3.19.0 ≤ 3.19.3; 3.20 ≤ 3.20.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5512 21 Apr 2026 3.14.0 ≤ 3.14.25; 3.15.0 ≤ 3.15.20; 3.16.0 ≤ 3.16.16; 3.17.0 ≤ 3.17.13; 3.18.0 ≤ 3.18.7; 3.19.0 ≤ 3.19.4; 3.20.0 < 3.20.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-4296 21 Apr 2026 3.14.0 ≤ 3.14.25; 3.15.0 ≤ 3.15.20; 3.16.0 ≤ 3.16.16; 3.17.0 ≤ 3.17.13; 3.18.0 ≤ 3.18.7; 3.19.0 ≤ 3.19.4; 3.20.0 < 3.20.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5921 21 Apr 2026 3.14.0 < 3.14.26; 3.15.0 < 3.15.21; 3.16.0 < 3.16.17; 3.17.0 < 3.17.14; 3.18.0 < 3.18.8; 3.19.0 < 3.19.5; 3.20.0 < 3.20.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-3582 10 Mar 2026 3.16.0 ≤ 3.16.14; 3.17.0 ≤ 3.17.11; 3.18.0 ≤ 3.18.5; 3.19.0 ≤ 3.19.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-2266 10 Mar 2026 3.18.0 ≤ 3.18.5; 3.19.0 ≤ 3.19.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-3306 10 Mar 2026 3.14.0 ≤ 3.14.23; 3.15.0 ≤ 3.15.18; 3.16.0 ≤ 3.16.14; 3.17.0 ≤ 3.17.11; 3.18.0 ≤ 3.18.5; 3.19.0 ≤ 3.19.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-3854 10 Mar 2026 3.14.0 ≤ 3.14.24; 3.15.0 ≤ 3.15.19; 3.16.0 ≤ 3.16.15; 3.17.0 ≤ 3.17.12; 3.18.0 ≤ 3.18.6; 3.19.0 ≤ 3.19.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-1999 18 Feb 2026 3.17.0 < 3.17.11; 3.18.0 < 3.18.5; 3.19.0 < 3.19.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-1355 18 Feb 2026 3.19.0 ≤ 3.19.1; 3.18.0 ≤ 3.18.4; 3.17.0 ≤ 3.17.10; 3.16.0 ≤ 3.16.13; 3.15.0 ≤ 3.15.17; 3.14.0 ≤ 3.14.22 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0573 18 Feb 2026 3.14 ≤ 3.14.21; 3.15 ≤ 3.15.16; 3.16 ≤ 3.16.12; 3.17 ≤ 3.17.9; 3.18 ≤ 3.18.3; 3.19 ≤ 3.19.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-13744 6 Jan 2026 3.14.0 ≤ 3.14.19; 3.15.0 ≤ 3.15.14; 3.16.0 ≤ 3.16.10; 3.17.0 ≤ 3.17.7; 3.18.0 ≤ 3.18.1; 3.19 ≤ 3.19.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-14046 11 Dec 2025 3.18.0 ≤ 3.18.2; 3.17.0 ≤ 3.17.8; 3.16.0 ≤ 3.16.11; 3.15.0 ≤ 3.15.15; 3.14.0 ≤ 3.14.20 3.19.0 Update reference ↗
CVE-2025-11578 10 Nov 2025 3.14 ≤ 3.14.19; 3.15 ≤ 3.15.14; 3.16 ≤ 3.16.10; 3.17 ≤ 3.17.7; 3.18 ≤ 3.18.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-11892 10 Nov 2025 3.18.0 < 3.18.1; 3.17.0 ≤ 3.17.6; 3.16.0 ≤ 3.16.9; 3.15.0 ≤ 3.15.13; 3.14.0 ≤ 3.14.18 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2025-8447 26 Aug 2025 3.14 ≤ 3.14.16; 3.15 ≤ 3.15.11; 3.16 ≤ 3.16.7; 3.17 ≤ 3.17.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-6981 15 Jul 2025 3.14.0 < 3.14.15; 3.15.0 < 3.15.10; 3.16.0 < 3.16.6; 3.17.0 < 3.17.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-3509 17 Apr 2025 3.13.0 ≤ 3.13.15; 3.14.0 ≤ 3.14.12; 3.15.0 ≤ 3.15.7; 3.16.0 ≤ 3.16.3; 13.17.0 < 13.17.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-3124 17 Apr 2025 3.13.0 ≤ 3.13.13; 3.14.0 ≤ 3.14.10; 3.15.0 ≤ 3.15.5; 3.16.0 ≤ 3.16.1 3.17.0 Update reference ↗
CVE-2024-10001 29 Jan 2025 3.11.0 ≤ 3.11.16; 3.12.0 ≤ 3.12.10; 3.13.0 ≤ 3.13.5; 3.14.0 ≤ 3.14.2; 3.15.0 ≤ 3.15.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-23369 21 Jan 2025 3.12.0 ≤ 3.12.13; 3.13.0 ≤ 3.13.9; 3.14.0 ≤ 3.14.6; 3.15.0 ≤ 3.15.1 3.16.0 Update reference ↗
CVE-2024-8810 7 Nov 2024 3.10.0 ≤ 3.10.16; 3.11.0 ≤ 3.11.14; 3.12.0 ≤ 3.12.8; 3.13.0 ≤ 3.13.3; 3.14 ≤ 3.14.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-10824 7 Nov 2024 3.13.0 ≤ 3.13.1 3.13.2. Update reference ↗
CVE-2024-10007 7 Nov 2024 3.11.0 ≤ 3.11.16; 3.12.0 ≤ 3.12.10; 3.13.0 ≤ 3.13.5; 3.14.0 ≤ 3.14.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-9487 10 Oct 2024 3.11.0 ≤ 3.11.15; 3.12.0 ≤ 3.12.9; 3.13.0 ≤ 3.13.4; 3.14.0 ≤ 3.14.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-4985 20 May 2024 3.9.0 ≤ 3.9.14; 3.10.0 ≤ 3.10.11; 3.11.0 ≤ 3.11.9; 3.12.0 ≤ 3.12.3 3.13.0 Update reference ↗
CVE-2024-2440 19 Apr 2024 3.9 ≤ 3.9.12; 3.10 ≤ 3.10.9; 3.11 ≤ 3.11.7; 3.12 ≤ 3.12.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-3684 19 Apr 2024 3.9.0 < 3.9.13; 3.10.0 < 3.10.10; 3.11.0 < 3.11.8; 3.12.0 < 3.12.2 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.