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

huggingface

huggingface/transformers

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-9856 2 Aug 2026 unspecified < 5.10.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-5241 3 Jun 2026 huggingface/transformers: unspecified < 5.5.0 RHSA-2026:42644: Red Hat OpenShift AI 2.25 Update reference ↗
CVE-2026-4372 24 May 2026 unspecified < 5.3.0 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-2026-1839 7 Apr 2026 unspecified < v5.0.0rc3 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-6921 23 Sep 2025 unspecified < 4.53.0 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-6051 14 Sep 2025 huggingface/transformers: unspecified < 4.53.0 4.53.0. Update reference ↗
CVE-2025-6638 12 Sep 2025 unspecified < 4.53.0 4.53.0. Update reference ↗
CVE-2025-5197 6 Aug 2025 unspecified < 4.53.0 4.53.0. Update reference ↗
CVE-2025-3933 11 Jul 2025 unspecified < 4.52.1 4.52.1. Update reference ↗
CVE-2025-3777 7 Jul 2025 unspecified < 4.52.1 4.52.1. Update reference ↗
CVE-2025-3264 7 Jul 2025 unspecified < 4.51.0 4.51.0. Update reference ↗
CVE-2025-3263 7 Jul 2025 unspecified < 4.51.0 4.51.0. Update reference ↗
CVE-2025-3262 7 Jul 2025 unspecified < 4.51.0 4.51.0. Update reference ↗
CVE-2025-2099 19 May 2025 unspecified < 4.50.0 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-1194 29 Apr 2025 unspecified < 4.50.0 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-12720 20 Mar 2025 unspecified < 4.48.0 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-3568 10 Apr 2024 unspecified < 4.38 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-7018 20 Dec 2023 unspecified < 4.36 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-6730 19 Dec 2023 unspecified < 4.36 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-2800 18 May 2023 unspecified < 4.30.0 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.