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

danny-avila

danny-avila/librechat

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-7105 2 Feb 2026 unspecified < v0.7.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-8849 30 Oct 2025 danny-avila/librechat: unspecified < v0.8.0-rc2 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-2025-8850 30 Oct 2025 danny-avila/librechat: unspecified < v0.8.0-rc2 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-2025-8848 22 Oct 2025 danny-avila/librechat: unspecified ≤ latest No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-7104 29 Sep 2025 unspecified < v0.7.9 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-2025-7106 23 Sep 2025 unspecified < v0.7.9 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-2025-6088 11 Sep 2025 unspecified < v0.7.9-rc1 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-2024-10359 20 Mar 2025 unspecified < 0.7.5 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-2024-11173 20 Mar 2025 unspecified < 0.7.6 0.7.6. Update reference ↗
CVE-2024-10363 20 Mar 2025 unspecified < 0.7.5 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-2024-11171 20 Mar 2025 unspecified < 0.7.6 0.7.6. Update reference ↗
CVE-2024-11172 20 Mar 2025 unspecified < 0.7.6 0.7.6. Update reference ↗
CVE-2024-11169 20 Mar 2025 unspecified < 0.7.6 0.7.6. Update reference ↗
CVE-2024-11167 20 Mar 2025 unspecified < 0.7.6 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-2024-10366 20 Mar 2025 unspecified < 0.7.5 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-2024-12580 20 Mar 2025 unspecified < 0.7.6 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-2024-10361 20 Mar 2025 unspecified < 0.7.5 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-2024-11170 20 Mar 2025 unspecified < 0.7.6 0.7.6. 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.