FFmpeg before commit 65b0dab contains an out-of-bounds read in the DASH demuxer (libavformat/dashdec.c). When a live DASH manifest is refreshed with a startNumber that is lower than the previous value, the current sequence number is driven negative. The fragment retrieval function checked only the upper bound before indexing the fragments array, allowing a negative index to be used and causing an out-of-bounds read. A malicious or misconfigured DASH server can trigger this by serving a live manifest with a decreasing startNumber across a manifest refresh.
CVE-2026-75146
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-19. a secondary CVSS source baseline 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(high)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 20, 2026
Advisory Details (3)
Auto-updated Aug 19, 2026FFmpeg Out-of-Bounds Read in DASH Demuxer via dashdec.c | Advisories | VulnCheck
https://www.vulncheck.com/advisories/ffmpeg-out-of-bounds-read-in-dash-demuxer-via-dashdec-cavformat/dashdec: reject a negative fragment index · 65b0dab903 - FFmpeg/FFmpeg - FFmpeg Forgejo
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/65b0dab903e5975e036b30ecc58f5935d4f151e0#24093 - avformat/dashdec: reject a negative fragment index - FFmpeg/FFmpeg - FFmpeg Forgejo
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/24093Vendor Advisories for CVE-2026-75146(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-21 04:30 UTCEG score recompute
- 2026-08-21 04:30 UTCGHSA enrichment
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 15:28 UTCEG score recompute
- 2026-08-20 15:28 UTCGHSA enrichment
- 2026-08-20 15:12 UTCEG score recompute
- 2026-08-20 15:12 UTCGHSA enrichment
- 2026-08-20 06:41 UTCEG score recompute
- 2026-08-20 06:41 UTCGHSA enrichment
- 2026-08-19 17:38 UTCEG score recompute
- 2026-08-19 16:44 UTCEG score recompute
- 2026-08-19 16:43 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-75146?
When was CVE-2026-75146 disclosed?
Is CVE-2026-75146 actively exploited?
What is the CVSS score of CVE-2026-75146?
How do I remediate CVE-2026-75146?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75146
Is Your Infrastructure Affected by CVE-2026-75146?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.