MEDIUM 5.5

CVE-2025-60473: MP4Box Null Pointer DoS Vulnerability – GPAC Patching Guide

A flaw in GPAC Project's MP4Box media processing tool (versions before 26.02.0) can be triggered by opening a specially crafted media file, causing the application to crash. The vulnerability stems from improper handling of null pointers in the filter chain processing logic. While the crash itself doesn't lead to data theft or system compromise, it disrupts media processing workflows and could be weaponized in batch processing environments to degrade service availability.

Source data · NVD / CISA · public domain

CVSS
3.1 · 5.5 MEDIUM · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Weaknesses (CWE)
CWE-476
Affected products
1 configuration(s)
Published / Modified
2026-06-25 / 2026-06-29

NVD description (verbatim)

A NULL pointer dereference in the gf_filter_in_parent_chain function (/filter_core/filter_pid.c) of GPAC Project/MP4Box before 26.02.0 allows attackers to cause a Denial of Service (DoS) via supplying a crafted file.

7 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2025-60473 is a null pointer dereference (CWE-476) located in the gf_filter_in_parent_chain function within /filter_core/filter_pid.c of GPAC before version 26.02.0. The vulnerability arises when the filter chain initialization fails to validate pointer state before dereferencing during filter hierarchy traversal. An attacker crafting a malformed media file with specific structural properties can trigger this unhandled exception, causing immediate process termination. The attack vector is local and requires user interaction (file opening), with no privilege escalation or privilege requirement.

Business impact

Organizations using MP4Box for automated media transcoding, format conversion, or batch processing face potential service disruption. If integrated into CI/CD pipelines, media processing jobs could fail unexpectedly, delaying content delivery or breaking build processes. For media asset management systems and broadcasting workflows, this DoS condition could disrupt operational efficiency. However, impact is contained to the affected process; the vulnerability does not enable data exfiltration, privilege escalation, or lateral movement.

Affected systems

GPAC Project's MP4Box tool in versions prior to 26.02.0 is affected. This includes standalone MP4Box installations and deployments where GPAC libraries are integrated into third-party media processing applications. Users running version 26.02.0 or later are not impacted. The vulnerability does not affect other GPAC components unless they directly invoke the vulnerable filter_pid.c code path.

Exploitability

Exploitation requires minimal technical sophistication—an attacker need only craft a media file with malformed filter chain metadata and deliver it to a user or system running vulnerable MP4Box. No network access, authentication, or special privileges are required. However, successful exploitation depends on user action (opening the file), limiting opportunistic exploitation. The low attack complexity and local vector make this suitable for targeted DoS campaigns against known MP4Box deployments, but widespread exploitation remains unlikely without active distribution of malicious files.

Remediation

Upgrade GPAC Project to version 26.02.0 or later. For organizations unable to patch immediately, implement input validation by restricting MP4Box to processing media from trusted sources only. Isolate media processing systems on segmented networks to contain potential DoS impact. Monitor for unexpected MP4Box process terminations and correlate with file ingestion events to detect exploitation attempts.

Patch guidance

Verify your GPAC version by running `mp4box -version` (or equivalent for your installation method). If the version is below 26.02.0, obtain the patched release from the official GPAC Project repository or your package manager. Test the patched version in a non-production environment with your typical media workflows before full deployment to ensure compatibility. Vendor advisories confirm that version 26.02.0 and later contain the necessary null pointer validation fix.

Detection guidance

Monitor for unexpected MP4Box crashes with segmentation faults or null pointer exceptions in filter_pid.c. Enable application logging if available to capture error signatures. In automated environments, alert on process exit codes indicating abnormal termination when processing media files. If available, use static analysis or fuzzing tools to identify other potential null pointer issues in media parsing code. Log file access patterns to correlate suspicious media files with application crashes.

Why prioritize this

This vulnerability warrants prompt but not emergency patching. While the CVSS score of 5.5 (MEDIUM) reflects availability impact only, organizations with media processing dependencies should treat this as a near-term priority. The ease of triggering (crafted file delivery) and potential for operational disruption in media workflows justify accelerated remediation, particularly for broadcasting, streaming, and transcoding services. The lack of KEV designation and absence of active exploitation reports suggest this remains a low-profile issue, allowing time for staged rollout.

Risk score, explained

The CVSS 3.1 score of 5.5 reflects a local attack vector (AV:L), low attack complexity (AC:L), no privilege requirement (PR:N), and user interaction necessary (UI:R). Confidentiality and integrity are unaffected (C:N/I:N), but availability suffers high impact (A:H) due to process termination. The score appropriately captures that this is a denial-of-service condition with low barrier to triggering but no systemic or data compromise risk. For critical media infrastructure, operational risk may exceed the numeric score.

Frequently asked questions

Can this vulnerability be exploited remotely?

No. The attack vector is local (AV:L), requiring the attacker or user to open a crafted file on the affected system. However, attackers could distribute malicious media files via email, download links, or compromised repositories to trick users into opening them.

Does this vulnerability affect media players like VLC or other applications using GPAC?

Only if those applications directly integrate GPAC's filter_pid.c code path and call gf_filter_in_parent_chain without proper validation. Most standalone media players have their own parsing logic. However, media processing tools, transcoding software, and custom applications built on GPAC are at risk.

What should I do if I cannot patch immediately?

Restrict MP4Box usage to trusted media sources, disable automated media processing from untrusted input, run MP4Box in isolated environments, and monitor for process crashes. Consider temporary workarounds such as pre-validating media files with separate tools before processing with MP4Box.

Is there an active exploit in the wild for this vulnerability?

No, this vulnerability is not included in CISA's Known Exploited Vulnerabilities (KEV) catalog, and no public exploits have been disclosed as of the knowledge cutoff. However, crafted test files demonstrating the DoS are straightforward to generate for anyone with basic media file knowledge.

This analysis is provided for informational purposes and reflects publicly available data as of June 2026. Security risk assessments are organization-specific; prioritization should account for your operational environment and asset exposure. Always verify patch applicability and test in non-production environments before deployment. SEC.co does not provide legal or compliance advice; consult your security and legal teams regarding regulatory obligations. Information in this document may change as additional research emerges; refer to official vendor advisories and CVSS vectors for authoritative technical details. Source: NVD (public-domain), retrieved 2026-08-02. Analysis generated by SEC.co (claude-haiku-4-5).