Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-59728: CWE-787 Out-of-bounds Write in FFmpeg MPEG-DASH

0
High
VulnerabilityCVE-2025-59728cvecve-2025-59728cwe-787
Published: Mon Oct 06 2025 (10/06/2025, 08:08:27 UTC)
Source: CVE Database V5
Vendor/Project: FFmpeg
Product: MPEG-DASH

Description

When calculating the content path in handling of MPEG-DASH manifests, there's an out-of-bounds NUL-byte write one byte past the end of the buffer.When we call xmlNodeGetContent below [0], it returns a buffer precisely allocated to match the string length, using strdup internally. If this buffer is not an empty string, it is assigned to root_url at [1].If the last (non-NUL) byte in this buffer is not '/' then we append '/' in-place at [2]. This will write two bytes into the buffer, starting at the last valid byte in the buffer, writing the NUL byte beyond the end of the allocated buffer. We recommend upgrading to version 8.0 or beyond.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 03:59:13 UTC

Technical Analysis

CVE-2025-59728 is an out-of-bounds write vulnerability classified under CWE-787, affecting the FFmpeg multimedia framework's handling of MPEG-DASH manifests. The issue arises during the calculation of the content path where the function xmlNodeGetContent returns a buffer allocated precisely to the string length using strdup. If this buffer is non-empty and does not end with a '/', the code attempts to append a '/' character in-place by writing two bytes starting at the last valid byte of the buffer. This results in a NUL byte being written one byte beyond the allocated buffer boundary, causing an out-of-bounds write. Such memory corruption can lead to undefined behavior including application crashes, data corruption, or potentially arbitrary code execution if exploited. The vulnerability affects FFmpeg versions including 7.1.1 and specific commits prior to version 8.0, which contains the fix. The CVSS 4.0 score is 8.7 (high severity), reflecting the vulnerability's potential impact on confidentiality, integrity, and availability, combined with the requirement for local or adjacent network access, low privileges, and high attack complexity. No user interaction is needed, but no known exploits have been reported in the wild. The vulnerability was publicly disclosed on October 6, 2025, and is assigned by Google.

Potential Impact

The out-of-bounds write vulnerability in FFmpeg's MPEG-DASH handling can lead to memory corruption, which may cause application crashes or enable attackers to execute arbitrary code within the context of the vulnerable process. This can compromise the confidentiality, integrity, and availability of systems processing MPEG-DASH streams using affected FFmpeg versions. Organizations relying on FFmpeg for media streaming, video processing, or content delivery may face service disruptions or potential system compromise. Given FFmpeg's widespread use in media servers, streaming platforms, and embedded devices, the impact can be significant, especially in environments where FFmpeg runs with elevated privileges or processes untrusted input. Although exploitation complexity is high and requires local or adjacent network access with low privileges, the absence of user interaction lowers the barrier for automated or scripted attacks in controlled environments. The lack of known exploits in the wild currently limits immediate risk, but the vulnerability remains a critical concern for media infrastructure security.

Mitigation Recommendations

To mitigate CVE-2025-59728, organizations should upgrade FFmpeg to version 8.0 or later, where the vulnerability has been addressed. Until upgrading is feasible, restrict access to systems running vulnerable FFmpeg versions to trusted users and networks to reduce the risk of exploitation. Implement strict input validation and sanitization for MPEG-DASH manifests to minimize the chance of triggering the vulnerability. Employ runtime protections such as memory safety tools (e.g., AddressSanitizer) during development and testing to detect out-of-bounds writes. Additionally, consider sandboxing or isolating FFmpeg processes to limit the impact of potential exploitation. Monitor security advisories and logs for unusual crashes or behavior indicative of exploitation attempts. Finally, maintain a robust patch management process to ensure timely application of security updates.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Google
Date Reserved
2025-09-19T08:11:37.549Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68e382204a42da91e7586492

Added to database: 10/6/2025, 8:47:28 AM

Last enriched: 2/27/2026, 3:59:13 AM

Last updated: 3/25/2026, 10:16:59 PM

Views: 415

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses