GStreamer vulnerabilities: known CVEs & security history
GStreamer · Media / Framework · 101 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all GStreamer release lines — 101 in total. A CVE here doesn't mean your version is affected — check GStreamer's current status and the safe version to run.
Known GStreamer CVEs
Actively-exploited and most-severe first. Showing the top 80 of 101. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2024-47615 | critical | 9.8 | 1% | 2024 |
| CVE-2024-47613 | critical | 9.8 | 1% | 2024 |
| CVE-2024-47607 | critical | 9.8 | 1% | 2024 |
| CVE-2024-47606 | critical | 9.8 | 1% | 2024 |
| CVE-2024-47540 | critical | 9.8 | 1% | 2024 |
| CVE-2024-47539 | critical | 9.8 | 1% | 2024 |
| CVE-2024-47538 | critical | 9.8 | 1% | 2024 |
| CVE-2024-47537 | critical | 9.8 | 1% | 2024 |
| CVE-2016-9636 | critical | 9.8 | 9% | 2017 |
| CVE-2016-9635 | critical | 9.8 | 9% | 2017 |
| CVE-2016-9634 | critical | 9.8 | 9% | 2017 |
| CVE-2024-47834 | critical | 9.1 | 1% | 2024 |
| CVE-2024-47777 | critical | 9.1 | 1% | 2024 |
| CVE-2024-47776 | critical | 9.1 | 1% | 2024 |
| CVE-2024-47775 | critical | 9.1 | 1% | 2024 |
| CVE-2024-47774 | critical | 9.1 | 1% | 2024 |
| CVE-2024-47600 | critical | 9.1 | 1% | 2024 |
| CVE-2024-47598 | critical | 9.1 | 1% | 2024 |
| CVE-2024-47597 | critical | 9.1 | 1% | 2024 |
| CVE-2026-3085 | high | 8.8 | 1% | 2026 |
| CVE-2026-3083 | high | 8.8 | 1% | 2026 |
| CVE-2025-3887 | high | 8.8 | 1% | 2025 |
| CVE-2024-0444 | high | 8.8 | 2% | 2024 |
| CVE-2023-50186 | high | 8.8 | 2% | 2024 |
| CVE-2023-44446 | high | 8.8 | 2% | 2024 |
| CVE-2023-44429 | high | 8.8 | 2% | 2024 |
| CVE-2023-40476 | high | 8.8 | 2% | 2024 |
| CVE-2023-40475 | high | 8.8 | 2% | 2024 |
| CVE-2023-40474 | high | 8.8 | 2% | 2024 |
| CVE-2023-38104 | high | 8.8 | 1% | 2024 |
| CVE-2023-38103 | high | 8.8 | 1% | 2024 |
| CVE-2023-37329 | high | 8.8 | 1% | 2024 |
| CVE-2023-37328 | high | 8.8 | 2% | 2024 |
| CVE-2023-37327 | high | 8.8 | 2% | 2024 |
| CVE-2019-9928 | high | 8.8 | 6% | 2019 |
| CVE-2025-47219 | high | 8.1 | 1% | 2025 |
| CVE-2026-3086 | high | 7.8 | 0% | 2026 |
| CVE-2026-3084 | high | 7.8 | 0% | 2026 |
| CVE-2026-3082 | high | 7.8 | 1% | 2026 |
| CVE-2026-3081 | high | 7.8 | 0% | 2026 |
| CVE-2026-2923 | high | 7.8 | 1% | 2026 |
| CVE-2026-2922 | high | 7.8 | 0% | 2026 |
| CVE-2026-2921 | high | 7.8 | 1% | 2026 |
| CVE-2026-2920 | high | 7.8 | 1% | 2026 |
| CVE-2025-6663 | high | 7.8 | 0% | 2025 |
| CVE-2025-2759 | high | 7.8 | 0% | 2025 |
| CVE-2024-4453 | high | 7.8 | 2% | 2024 |
| CVE-2022-2122 | high | 7.8 | 0% | 2022 |
| CVE-2022-1925 | high | 7.8 | 0% | 2022 |
| CVE-2022-1924 | high | 7.8 | 0% | 2022 |
| CVE-2022-1923 | high | 7.8 | 0% | 2022 |
| CVE-2022-1922 | high | 7.8 | 0% | 2022 |
| CVE-2022-1921 | high | 7.8 | 0% | 2022 |
| CVE-2022-1920 | high | 7.8 | 0% | 2022 |
| CVE-2021-3498 | high | 7.8 | 2% | 2021 |
| CVE-2021-3497 | high | 7.8 | 1% | 2021 |
| CVE-2016-9447 | high | 7.8 | 3% | 2017 |
| CVE-2016-9809 | high | 7.8 | 3% | 2017 |
| CVE-2024-47835 | high | 7.5 | 1% | 2024 |
| CVE-2024-47778 | high | 7.5 | 1% | 2024 |
| CVE-2024-47603 | high | 7.5 | 1% | 2024 |
| CVE-2024-47602 | high | 7.5 | 1% | 2024 |
| CVE-2024-47601 | high | 7.5 | 1% | 2024 |
| CVE-2024-47599 | high | 7.5 | 1% | 2024 |
| CVE-2024-47596 | high | 7.5 | 1% | 2024 |
| CVE-2024-47546 | high | 7.5 | 1% | 2024 |
| CVE-2024-47545 | high | 7.5 | 1% | 2024 |
| CVE-2024-47544 | high | 7.5 | 1% | 2024 |
| CVE-2024-47543 | high | 7.5 | 1% | 2024 |
| CVE-2024-47542 | high | 7.5 | 1% | 2024 |
| CVE-2024-47541 | high | 7.5 | 1% | 2024 |
| CVE-2017-5848 | high | 7.5 | 4% | 2017 |
| CVE-2017-5847 | high | 7.5 | 4% | 2017 |
| CVE-2017-5845 | high | 7.5 | 4% | 2017 |
| CVE-2017-5843 | high | 7.5 | 4% | 2017 |
| CVE-2017-5841 | high | 7.5 | 4% | 2017 |
| CVE-2017-5840 | high | 7.5 | 5% | 2017 |
| CVE-2017-5839 | high | 7.5 | 4% | 2017 |
| CVE-2017-5838 | high | 7.5 | 5% | 2017 |
| CVE-2016-10199 | high | 7.5 | 4% | 2017 |
21 older / lower-severity CVEs not shown — see GStreamer's full record.
Is my GStreamer version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your GStreamer version → · Monitor GStreamer for new CVEs →
GStreamer vulnerabilities — frequently asked
How many known vulnerabilities does GStreamer have?
IsItPatched tracks 101 CVEs for GStreamer. 19 are critical-severity and 66 high-severity. These span every release line — what matters is whether the version you run is affected.
Does GStreamer have any actively-exploited vulnerabilities?
None of GStreamer's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.
What is the most severe GStreamer vulnerability?
Among tracked issues, CVE-2024-47615 (CRITICAL, CVSS 9.8) ranks highest — a Out-of-bounds write weakness.
Is GStreamer safe to use?
It depends on the version. The latest supported GStreamer release (1.28.4) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: GStreamer security status · GStreamer end-of-life · actively-exploited CVEs. Always verify against GStreamer's advisories — see our disclaimer.