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

JetBrains

YouTrack

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 CVE identity is linked to the Lifecycle record YouTrack. 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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-86482 7 Sep 2026 YouTrack: < 2026.2.18634 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-86481 7 Sep 2026 < 2026.2.18634 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-86479 7 Sep 2026 < 2026.2.18788, 2026.1.14055, 2025.3.161254 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-86478 7 Sep 2026 < 2025.3.161254, 2026.1.14042 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-75051 17 Aug 2026 YouTrack: < 2026.2.17917 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-75050 17 Aug 2026 YouTrack: < 2026.1.13901, 2026.2.17950 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-75049 17 Aug 2026 YouTrack: < 2026.1.13903, 2026.2.17950 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-75048 17 Aug 2026 YouTrack: < 2026.2.18068 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-75047 17 Aug 2026 YouTrack: < 2026.2.18177 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-75046 17 Aug 2026 YouTrack: < 2026.2.18112 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-75045 17 Aug 2026 YouTrack: < 2025.3.156085, 2026.1.13913, 2026.2.18112 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-75044 17 Aug 2026 YouTrack: < 2025.3.156085, 2026.1.13914, 2026.2.18095 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-62422 14 Jul 2026 < 2026.1.13757, 2025.3.148033, 2025.2.148048, 2025.1.148120, 2024.3.148430, 2024.2.148429 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-61492 10 Jul 2026 < 2026.2.17394 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-59791 10 Jul 2026 < 2026.2.17012 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-57926 26 Jun 2026 < 2026.2.16593 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-57925 26 Jun 2026 < 2026.2.16593 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-57924 26 Jun 2026 < 2026.2.16593 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-57923 26 Jun 2026 < 2026.2.16593 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-57922 26 Jun 2026 < 2026.2.16593 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-57921 26 Jun 2026 < 2026.2.16593 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-49386 29 May 2026 < 2026.1.13570 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-49385 29 May 2026 < 2026.1.13570 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-49370 29 May 2026 < 2026.1.13162 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-49369 29 May 2026 < 2026.1.13162 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-49368 29 May 2026 < 2026.1.13162 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-33392 17 Apr 2026 < 2025.3.131383 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-28193 25 Feb 2026 < 2025.3.121962 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-25846 9 Feb 2026 < 2025.3.119033 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64773 11 Nov 2025 < 2025.3.104432 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64685 10 Nov 2025 < 2025.3.104432 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-64684 10 Nov 2025 < 2025.3.104432 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-57731 20 Aug 2025 < 2025.2.92387 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-54527 28 Jul 2025 < 2025.2.86935, 2025.2.87167, 2025.3.87341, 2025.3.87344 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-53959 15 Jul 2025 < 2025.2.86069, 2024.3.85077, 2025.1.86199 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-47850 20 May 2025 < 2025.1.74704 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-48391 20 May 2025 < 2025.1.76253 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-24458 21 Jan 2025 < 2024.3.55417 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-24457 21 Jan 2025 < 2024.3.55417 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-54158 4 Dec 2024 < 2024.3.52635 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-54157 4 Dec 2024 < 2024.3.52635 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-54156 4 Dec 2024 < 2024.3.52635 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-54155 4 Dec 2024 < 2024.3.51866 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-54154 4 Dec 2024 < 2024.3.51866 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-54153 4 Dec 2024 < 2024.3.51866 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-50582 28 Oct 2024 < 2024.3.47707 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-50581 28 Oct 2024 < 2024.3.47707 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-50580 28 Oct 2024 < 2024.3.47707 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-50579 28 Oct 2024 < 2024.3.47707 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-50578 28 Oct 2024 < 2024.3.47707 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.