FFmpeg through 8.1.2, fixed in commit aafb5c6, contains a signed integer overflow vulnerability in the MACE6 audio decoder that allows attackers to corrupt heap memory by supplying a crafted CAF file with a malicious bytes_per_packet value. Attackers can craft a CAF file with oversized bytes_per_packet and frames_per_packet values in the desc chunk to trigger an integer overflow in mace_decode_frame() during output sample count computation, resulting in an undersized buffer allocation and heap out-of-bounds write that could enable code execution.
CVE-2026-66039
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. a secondary CVSS source baseline 8.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
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity88% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 35%
- KEV
- Not listed
Published
July 24, 2026
Last Modified
July 24, 2026
Advisory Details (3)
Auto-updated Jul 24, 2026FFmpeg MACE6 Audio Decoder Heap Out-of-Bounds Write via CAF File | Advisories | VulnCheck
https://www.vulncheck.com/advisories/ffmpeg-mace6-audio-decoder-heap-out-of-bounds-write-via-caf-fileavcodec/mace: reject sample counts that overflow int · aafb5c655e - FFmpeg/FFmpeg - FFmpeg Forgejo
https://code.ffmpeg.org/FFmpeg/FFmpeg/commit/aafb5c655edc76a753275c383ebb139feb032718#23631 - avcodec/mace: reject sample counts that overflow int - FFmpeg/FFmpeg - FFmpeg Forgejo
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/23631Vendor Advisories for CVE-2026-66039(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 10× in last 7d / 10× 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-26 15:46 UTCEG score recompute
- 2026-07-26 15:46 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 02:55 UTCEG score recompute
- 2026-07-26 02:55 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 20:12 UTCEG score recompute
- 2026-07-24 20:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-190 · CWE-122
Frequently asked(5)
What is CVE-2026-66039?
When was CVE-2026-66039 disclosed?
Is CVE-2026-66039 actively exploited?
What is the CVSS score of CVE-2026-66039?
How do I remediate CVE-2026-66039?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-66039
Is Your Infrastructure Affected by CVE-2026-66039?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.