CVE-2026-107695FFmpeg before 8.1.3 HLS Demuxer Infinite Loop via Self-Referencing Playlist
Updated under an hour ago ()
Does this affect you?
It affects FFmpeg. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
FFmpeg before 8.1.3 contains an infinite loop vulnerability in the HLS demuxer that allows remote attackers to cause denial of service because parse_playlist() accepts Master Playlist tags inside Media Playlists. Attackers can trick victims into opening a crafted self-referencing playlist that endlessly adds variants in hls_read_header(), causing unbounded CPU and I/O consumption.
- CVSS
- 6.5 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- Weakness (CWE)
- CWE-835
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- VulnCheck
- NVD analysis
- Analyzed
- Record last updated
- Oct 14, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
FFmpeg FFmpeg ffmpeg:ffmpeg (from the name) | before 8.1.3 | CNA record |
ffmpeg ffmpeg ffmpeg:ffmpeg | before 8.1.3 | NVD |
References
- https://github.com/FFmpeg/FFmpeg/commit/c364ab176f722bdabc886845e770c9eacbc1e3e5patch
- https://github.com/FFmpeg/FFmpeg/commit/0e6eef35517apatch
- https://github.com/FFmpeg/FFmpeg/commit/a4ddaba8bb78patch
- https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/23618patch, issue-tracking
- https://github.com/FFmpeg/FFmpeg/blob/n8.1.2/libavformat/hls.c#L866technical-description, product
- https://gist.github.com/OxBat/59574a2940092cda1b6e76bbf96f53d0exploit, mitigation, third-party-advisory
- https://github.com/FFmpeg/FFmpegproduct
- https://www.vulncheck.com/advisories/ffmpeg-before-8.1.3-hls-demuxer-infinite-loop-via-self-referencing-playlistthird-party-advisory, patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.