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

Blender

Blender

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 Blender. 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-60103 13 Jul 2026 3.0.0 ≤ 5.1.2 968972a918b5ed2d534295b639c54449d7de11cd Update reference ↗
CVE-2017-2918 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-2908 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-2907 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-2906 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-2905 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-2904 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-2903 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-2902 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-2901 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-2900 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-2899 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-12105 24 Apr 2018 v2.78c (32-bit) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-12104 24 Apr 2018 v2.78c (32-bit) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-12103 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-12102 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-12101 24 Apr 2018 v2.78c (32-bit) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-12100 24 Apr 2018 v2.78c (32-bit) No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-12099 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-12086 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-12082 24 Apr 2018 v2.78c No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-12081 24 Apr 2018 v2.78c 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.