FFmpeg through 8.1.2 contains an out-of-bounds write vulnerability that allows attackers to cause heap corruption by supplying a crafted ffconcat file processed with the -safe 0 flag. The TY demuxer's demux_audio() function decrements packet size without bounds checking, producing a negative size value that is passed to memcpy() in shorten_decode_frame(), where conversion to size_t wraps the value to near SIZE_MAX and triggers reads beyond the source allocation and writes far beyond the Shorten decoder's bitstream buffer.
CVE-2026-65704
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-23. the CNA's CVSS baseline 7.8; 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
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 35(Track)EG Risk 35/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 computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
July 23, 2026
Last Modified
July 28, 2026
Advisory Details (3)
Auto-updated Jul 23, 2026FFmpeg 8.1.2 Out-of-Bounds Write via TY Demuxer and Shorten Decoder | Advisories | VulnCheck
https://www.vulncheck.com/advisories/ffmpeg-out-of-bounds-write-via-ty-demuxer-and-shorten-decoderavformat/ty: don't let the Series2 AC3 trim underflow the packet size · de771bd527 - FFmpeg/FFmpeg - FFmpeg Forgejo
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/de771bd52774a52d45b0e2c82e56995a1ef40df7#23767 - avformat/ty: don't let the Series2 AC3 trim underflow the packet size - FFmpeg/FFmpeg - FFmpeg Forgejo
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/23767Vendor Advisories for CVE-2026-65704(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 15× 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-07-28 01:30 UTCEG score recompute
- 2026-07-28 01:30 UTCGHSA enrichment
- 2026-07-27 20:44 UTCGHSA enrichment
- 2026-07-27 15:42 UTCGHSA enrichment
- 2026-07-27 03:30 UTCGHSA enrichment
- 2026-07-26 15:18 UTCEG score recompute
- 2026-07-26 15:18 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:07 UTCEG score recompute
- 2026-07-26 03:07 UTCGHSA enrichment
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 19:22 UTCEG score recompute
- 2026-07-23 19:21 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-191 · CWE-787
Frequently asked(5)
What is CVE-2026-65704?
When was CVE-2026-65704 disclosed?
Is CVE-2026-65704 actively exploited?
What is the CVSS score of CVE-2026-65704?
How do I remediate CVE-2026-65704?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65704
Is Your Infrastructure Affected by CVE-2026-65704?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.