← Search results
CVE-LINKED INVENTORY44 SECURITY RECORDS
FFMPEG
FFMPEG
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record FFmpeg. 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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-96611 | 23 Sep 2026 | FFmpeg: < 9.0 | Update to FFmpeg commit 059eb2e853 or later. | Update reference ↗ |
| CVE-2026-52297 | 13 Sep 2026 | FFmpeg: < 9.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-52296 | 13 Sep 2026 | FFmpeg: < 9.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-52295 | 1 Sep 2026 | FFmpeg: < 9.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-75147 | 19 Aug 2026 | < 983dae9c19f46c87d597598c0fd2f2fcee0ad2f8 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-75146 | 19 Aug 2026 | < 65b0dab903e5975e036b30ecc58f5935d4f151e0 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-75145 | 19 Aug 2026 | < b4c199c5906ff53368926c2a5839881f41957e7f | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-75144 | 19 Aug 2026 | < 1cdeb3c4e7f1f8566d846b9b451e01c376398818 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-75143 | 19 Aug 2026 | < 1c10bcc2e17255dacb717a25ab3db142ce390602 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-75142 | 19 Aug 2026 | < 9d786e4b5e9b8482651928574de33772aeee7be1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-75141 | 19 Aug 2026 | < acf5d7cdc1f9ae8752c23e1ea8d7f355ed780781 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-70632 | 6 Aug 2026 | 4.4 < 9.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-70631 | 6 Aug 2026 | 0.5 < 9.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-70630 | 6 Aug 2026 | 3.0 < 9.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-70629 | 6 Aug 2026 | 3.0 < 9.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-70628 | 6 Aug 2026 | 0.5 < 9.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-66041 | 24 Jul 2026 | 7.0 ≤ 8.1.2 | 4da9812e25894fb51d62a8875cfa8eb39b5e20f5 | Update reference ↗ |
| CVE-2026-66040 | 24 Jul 2026 | ≤ 8.1.2 | b506fafec9a19fcbc2be5271875fd4a63d6615bc | Update reference ↗ |
| CVE-2026-66039 | 24 Jul 2026 | ≤ 8.1.2 | aafb5c655edc76a753275c383ebb139feb032718 | Update reference ↗ |
| CVE-2026-66038 | 24 Jul 2026 | ≤ 8.1.2 | 86708357d126af84c16f80d9c57335d1e8c845c5 | Update reference ↗ |
| CVE-2026-66037 | 24 Jul 2026 | ≤ 8.1.2 | 86708357d126af84c16f80d9c57335d1e8c845c5 | Update reference ↗ |
| CVE-2026-66036 | 24 Jul 2026 | ≤ 8.1.2 | 5d7112c60e6f0f0742ce47d448e6da0718a70f4c | Update reference ↗ |
| CVE-2026-65706 | 23 Jul 2026 | 3.0 ≤ 8.1.2 | a7e38b617b32f996beaa371bbf04b39907d7a527 | Update reference ↗ |
| CVE-2026-65705 | 23 Jul 2026 | 3.4 ≤ 8.1.2 | f186c50cf53aec20e9a29059cb22ca3f2d59201c | Update reference ↗ |
| CVE-2026-65704 | 23 Jul 2026 | ≤ 8.1.2 | de771bd52774a52d45b0e2c82e56995a1ef40df7 | Update reference ↗ |
| CVE-2026-65703 | 23 Jul 2026 | 2.7 ≤ 8.1.2 | fd3ee52fab34d98a95b787d0b5ff45685766200c | Update reference ↗ |
| CVE-2026-64835 | 22 Jul 2026 | 4.4 ≤ 8.1.2; 1836ef96846937a6cc2443698a693104f5c0b21e | Backport CVE fixes from upstream | Update reference ↗ |
| CVE-2026-64834 | 22 Jul 2026 | 0.6.3 ≤ 8.1.2; 11d5f475be95d22d5f0692220cc772b116abc632 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-64833 | 22 Jul 2026 | 0.7.1 ≤ 8.1.2; 6f80e2765492700622596af720534cef33dd31b4 | 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-64832 | 22 Jul 2026 | 4.4 ≤ 8.1.2; 4c6217477fc64305055b37d9d1d0d76d30e37f97 | 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-64831 | 22 Jul 2026 | 8.0 ≤ 8.1.2; 92737390dc133daadce47dd7d2ec8ef3d9ebcbed | 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-64830 | 22 Jul 2026 | 2.1 ≤ 8.1.2; dbd495f066a85ba96b17433f4306582aa37c3951 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-58049 | 28 Jun 2026 | FFmpeg: ≤ bcd2c69e087a09b07cf45c6bd2428ee1ccb2925c | RHSA-2026:52832: Red Hat Enterprise Linux AI 3.0 for RHEL 9 | Update reference ↗ |
| CVE-2026-8461 | 18 Jun 2026 | < 8.1.2 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2026-40962 | 16 Apr 2026 | 4.1 < 8.1 | Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 | Update reference ↗ |
| CVE-2025-59734 | 6 Oct 2025 | 4d7c609be37dc57d31527c8c9e5945dc9491a7cd < 8.0; 7.1.1 < 8.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59733 | 6 Oct 2025 | 9a32b863074ed4140141e0d3613905c6f1fe61c5 < 8.0; 7.1.1 < 8.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59732 | 6 Oct 2025 | 9a32b863074ed4140141e0d3613905c6f1fe61c5 < 8.0; 7.1.1 < 8.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59731 | 6 Oct 2025 | 9a32b863074ed4140141e0d3613905c6f1fe61c5 < 8.0; 7.1.1 < 8.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59730 | 6 Oct 2025 | 829680f96a7a7ff02d1543895ec0fb713309d5c0 < 8.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59729 | 6 Oct 2025 | a218cafe4d3be005ab0c61130f90db4d21afb5db < 8.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-9951 | 9 Sep 2025 | < 8.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-0518 | 16 Jan 2025 | 7.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-2022-2566 | 23 Sep 2022 | 5.1 < unspecified; ab77b878f1205225c6de1370fb0e998dbcc8bc69 < unspecified; unspecified < c953baa084607dd1d84c3bfcce3cf6a87c3e6e05 | 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.