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

Adobe

Substance3D - Sampler

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-2025-54205 12 Aug 2025 ≤ 5.0.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-43581 10 Jun 2025 ≤ 5.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-43588 10 Jun 2025 ≤ 5.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-24444 11 Mar 2025 ≤ 4.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-24443 11 Mar 2025 ≤ 4.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-24441 11 Mar 2025 ≤ 4.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-24445 11 Mar 2025 ≤ 4.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-24442 11 Mar 2025 ≤ 4.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-24439 11 Mar 2025 ≤ 4.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-24440 11 Mar 2025 ≤ 4.5.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-52996 10 Dec 2024 ≤ 4.5.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-52994 10 Dec 2024 ≤ 4.5.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-52995 10 Dec 2024 ≤ 4.5.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-47459 17 Oct 2024 ≤ 4.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-41862 14 Aug 2024 ≤ 4.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-41861 14 Aug 2024 ≤ 4.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-41860 14 Aug 2024 ≤ 4.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-41863 14 Aug 2024 ≤ 4.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-48625 13 Dec 2023 ≤ 4.2.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2023-48627 13 Dec 2023 ≤ 4.2.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2023-48628 13 Dec 2023 ≤ 4.2.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2023-48630 13 Dec 2023 ≤ 4.2.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2023-48629 13 Dec 2023 ≤ 4.2.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2023-48626 13 Dec 2023 ≤ 4.2.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗

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.