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

EmbedAI

EmbedAI

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-0747 30 Jan 2025 < 2.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-0746 30 Jan 2025 < 2.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-0745 30 Jan 2025 < 2.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-0744 30 Jan 2025 < 2.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-0743 30 Jan 2025 < 2.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-0742 30 Jan 2025 < 2.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-0741 30 Jan 2025 < 2.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-0740 30 Jan 2025 < 2.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-0739 30 Jan 2025 < 2.1 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.