dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2025-59728

HIGH · 8.7 CVSS v4.0 Published 2025-10-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Heap-based buffer overflow in MPEG-DASH manifest handling. The code uses xmlNodeGetContent which returns a buffer sized exactly to the string length. When appending a '/' character to the path, it writes two bytes starting at the last valid byte, causing the NUL terminator to be written one byte beyond the allocated buffer.

MitigationUpgrade to version 8.0 or later to receive the patch for this out-of-bounds write vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
High
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify software with MPEG-DASH manifest handling
    Search for applications or libraries that process MPEG-DASH streams or .mpd manifest files. Look for binaries or libraries that include DASH or MPEG-DASH in their name or documentation, or check for dependencies on XML parsing libraries like libxml2.
    Affected if The system runs any software that parses MPEG-DASH manifests (.mpd files) using XML functions
  2. Check the installed version against the affected range
    Run 'version' or '-V' commands on the identified DASH-handling software, or check library package versions (e.g., dpkg -l, rpm -qi). Compare against the known affected versions (all versions before 8.0).
    Affected if The installed version is earlier than 8.0
  3. Inspect application logs, configuration, or runtime behavior for evidence of .mpd file loading or DASH stream playback. Use process monitoring (e.g., strace, lsof) to observe XML file operations during media playback.
    Affected if The software actively loads or parses DASH manifests at runtime
  4. Verify XML library usage in the component
    If the software uses embedded or external XML parsing, confirm it uses xmlNodeGetContent or similar functions for manifest handling. This may require checking build configurations, source code, or library dependencies.
    Affected if The manifest parser uses xmlNodeGetContent for path extraction

A user is affected if they run software with MPEG-DASH manifest parsing capability that is version 8.0 or earlier, and that software actively processes DASH streams using the vulnerable XML function.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 8.0 or later to receive the patch for this out-of-bounds write vulnerability.

Recommended fix Moderate confidence

Version 8.0 or later (as specified in the vendor recommendation)

  1. 1. Identify the specific software product using MPEG-DASH manifest parsing in your environment
  2. 2. Consult the vendor's release notes or issue tracker at issuetracker.google.com to confirm the exact vulnerable versions
  3. 3. Plan for upgrade testing, especially around MPEG-DASH manifest handling features
  4. 4. Perform upgrade to version 8.0 or any later stable release
  5. 5. Validate that MPEG-DASH content playback functions correctly after upgrade
Caveat Review release notes for version 8.0 for any API or behavioral changes that may affect existing MPEG-DASH workflows

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59728 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59728 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data