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

JetBrains

TeamCity

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 JetBrains TeamCity. 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-2023-38066 12 Jul 2023 < 2023.05.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-38065 12 Jul 2023 < 2023.05.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-38064 12 Jul 2023 < 2023.05.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-38063 12 Jul 2023 < 2023.05.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-38062 12 Jul 2023 < 2023.05.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-38061 12 Jul 2023 < 2023.05.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2015-1313 29 Jun 2023 8.0.1 < 9.0.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34229 31 May 2023 < 2023.05 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34228 31 May 2023 < 2023.05 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34227 31 May 2023 < 2023.05 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34226 31 May 2023 < 2023.05 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34225 31 May 2023 < 2023.05 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34224 31 May 2023 < 2023.05 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34223 31 May 2023 < 2023.05 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34222 31 May 2023 < 2023.05 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34221 31 May 2023 < 2023.05 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34220 31 May 2023 < 2023.05 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34219 31 May 2023 < 2023.05 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-34218 31 May 2023 < 2023.05 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-48428 27 Mar 2023 < 2022.10.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-48427 27 Mar 2023 < 2022.10.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-48426 27 Mar 2023 < 2022.10.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-48344 23 Feb 2023 < 2022.10.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-48343 23 Feb 2023 < 2022.10.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-48342 23 Feb 2023 < 2022.10.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-46831 8 Dec 2022 2022.10 < 2022.10.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-46830 8 Dec 2022 2022.10 < 2022.10.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-44646 3 Nov 2022 2022.10 < 2022.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-44624 3 Nov 2022 2022.10 < 2022.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-44623 3 Nov 2022 2022.10 < 2022.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-44622 3 Nov 2022 2022.10 < 2022.10; 2021.2 < 2021.2* No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-40979 23 Sep 2022 2022.04.4 < 2022.04.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-38133 10 Aug 2022 2022.04.3 < 2022.04.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-36322 20 Jul 2022 2022.04.2 < 2022.04.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-36321 20 Jul 2022 2022.04.2 < 2022.04.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29929 12 May 2022 2022.04 < 2022.04 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29928 12 May 2022 2022.04 < 2022.04 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29927 12 May 2022 2022.04 < 2022.04 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.