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

Autodesk

Shared Components

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-14255 2 Sep 2026 1.11.0 < 1.12.0; 2.0.0 < 2.2.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0875 18 Feb 2026 1.9.0.7 < 1.10.0.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-0874 18 Feb 2026 1.9.0.7 < 1.10.0.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10900 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10899 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10898 15 Dec 2025 Shared Components: 1.8.0 < 1.9.0; AutoCAD: 2025.0.0 < 2025.1.4, 2024.0.0 < 2024.1.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10889 15 Dec 2025 Shared Components: 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10888 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10887 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10886 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10884 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10883 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10882 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-10881 15 Dec 2025 Shared Components: 1.8.0 < 1.9.0; AutoCAD: 2025.0.0 < 2025.1.4, 2024.0.0 < 2024.1.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-9460 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-9459 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-9457 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-9456 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-9455 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-9454 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-9453 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-9452 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-14593 15 Dec 2025 1.8.0.7 < 1.9.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-9458 7 Nov 2025 1.7.0.10 < 1.8.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-8892 22 Sep 2025 1.6.2.11 < 1.8.0.7 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7675 29 Jul 2025 1.6.2.11 < 1.7.0.10; 2025 < 2025.1.3; 2024 < 2024.1.8; 2023 < 2023.1.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7497 29 Jul 2025 1.6.2.11 < 1.7.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-6637 29 Jul 2025 1.6.2.11 < 1.7.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-6636 29 Jul 2025 1.6.2.11 < 1.7.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-6635 29 Jul 2025 1.6.2.11 < 1.7.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-6631 29 Jul 2025 1.6.2.11 < 1.7.0.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-5043 29 Jul 2025 1.6.2.11 < 1.7.0.10; 2025 < 2025.1.3; 2024 < 2024.1.8; 2023 < 2023.1.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-5038 29 Jul 2025 1.6.2.11 < 1.7.0.10; 2025 < 2025.1.3; 2024 < 2024.1.8; 2023 < 2023.1.8 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.