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

Autodesk

AutoCAD

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-2024-23153 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.5; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23152 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.5; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23151 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.5; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23150 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.5; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37006 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37005 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37004 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37003 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37002 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37001 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-37000 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23149 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23148 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23147 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23146 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23145 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23144 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23143 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23142 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23141 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23140 25 Jun 2024 2025 < 2025.1; 2024 < 2024.1.4; 2023 < 2023.1.6; 2022 < 2022.1.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23138 17 Mar 2024 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23137 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23136 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23135 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23134 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23133 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23132 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23131 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23130 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23129 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23128 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23127 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23126 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23125 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23124 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23123 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23122 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23121 22 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-23120 21 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-0446 21 Feb 2024 2025 < 2025.0.1; 2024 < 2024.1.3; 2023 < 2023.1.5; 2022 < 2022.1.4; 2021 < 2021.1.4 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.