CVE-2025-60467: GPAC MP4Box Use-After-Free DoS Vulnerability
GPAC Project's MP4Box, a multimedia framework tool, contains a flaw where freed memory is inadvertently accessed during specific filter cleanup operations. An attacker can exploit this by providing a maliciously crafted media file, crashing the application and disrupting service availability. This vulnerability affects versions before 26.02.0.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weaknesses (CWE)
- CWE-416
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-24 / 2026-06-29
NVD description (verbatim)
A use-after-free in the gf_filter_pid_inst_swap_delete_task 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 media file.
6 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2025-60467 is a use-after-free (UAF) vulnerability in the gf_filter_pid_inst_swap_delete_task function within GPAC's filter_core/filter_pid.c module. When processing certain media files, the function fails to properly manage memory references during filter instance deletion, allowing an attacker to trigger access to already-freed memory. This results in undefined behavior and process termination, constituting a denial-of-service condition. The vulnerability carries a CVSS 3.1 score of 7.5 (HIGH severity) due to its network-exploitable attack surface, lack of authentication requirements, and direct impact on availability.
Business impact
Organizations using GPAC/MP4Box for media processing pipelines face service disruption risks. If MP4Box processes user-supplied or untrusted media files—such as in transcoding services, media analysis platforms, or automated content ingestion workflows—a crafted file can crash the service. This can interrupt legitimate media operations, cause cascading failures in dependent services, and require manual intervention to restart affected systems. The impact is primarily operational availability rather than data confidentiality or integrity breach.
Affected systems
GPAC Project's MP4Box library and tools before version 26.02.0 are affected. Any software embedding GPAC or directly using the filter framework for multimedia processing inherits this risk. Common deployments include media servers, transcoding engines, content analysis tools, and multimedia SDKs integrated into streaming platforms or broadcast infrastructure.
Exploitability
Exploitability is straightforward: no authentication, privileges, or user interaction are required. An attacker needs only to deliver a specially crafted media file to a vulnerable instance. If the instance processes untrusted media from network sources, web uploads, or third-party feeds, the attack surface is direct. However, the vulnerability requires the specific code path to be exercised, which depends on the filter configuration used during media processing.
Remediation
Upgrade GPAC/MP4Box to version 26.02.0 or later. Verify the upgrade with your distribution or vendor, as backports may be available for older supported branches. Until patching is complete, restrict MP4Box processing to trusted media sources and consider sandboxing or containerizing the service to limit blast radius.
Patch guidance
Apply the patch by upgrading to GPAC version 26.02.0 or newer. Consult the official GPAC Project repository and release notes for verification. If your deployment uses a wrapper or integration library, verify that the underlying GPAC dependency is also updated. Test the patched version in a staging environment to ensure media processing workflows remain functional before deploying to production.
Detection guidance
Monitor for unexpected MP4Box or GPAC filter process crashes, particularly those coinciding with media file uploads or submissions. Log file analysis may reveal segmentation faults or memory access violations. Network-based detection is challenging absent application-level logging; focus on application-level signals. Consider collecting process exit codes and core dumps when available. In high-volume media processing environments, a sudden spike in process crashes correlated with specific file submissions may indicate exploitation attempts.
Why prioritize this
Despite a HIGH CVSS score, this vulnerability does not appear on the KEV catalog and is not currently exploited in the wild. However, the ease of exploitation and the direct availability impact warrant rapid patching in environments processing untrusted media. Prioritize based on whether your deployment processes external or user-submitted files; internal-only use cases can follow a standard patch cycle.
Risk score, explained
The CVSS 3.1 score of 7.5 reflects network accessibility (AV:N), low attack complexity (AC:L), no authentication (PR:N), no user interaction (UI:N), uniform scope (S:U), and high availability impact (A:H). The lack of confidentiality and integrity damage prevents a critical rating. The score is appropriate for a denial-of-service condition in a widely-used multimedia framework, but risk in your environment depends on whether untrusted media reaches vulnerable instances.
Frequently asked questions
Can this vulnerability be exploited remotely?
Yes. No authentication or user interaction is required; an attacker must only cause a vulnerable instance to process a crafted media file. In network-accessible deployments or those accepting user uploads, remote exploitation is feasible.
Does this affect only MP4 files, or other formats?
The vulnerability is in the filter framework's core; it can be triggered by various media formats processed through the affected code path. Not all file types or filter chains will trigger it, but assume a wide range of crafted media files could be weaponized.
What is the difference between this and other use-after-free bugs?
Use-after-free in cleanup code (like filter deletion) is particularly dangerous because it occurs during shutdown or task teardown, making it easy to reach from many input scenarios. Many legitimate operations may inadvertently trigger the vulnerable path.
If we only use MP4Box internally for known-good files, do we need to patch immediately?
Internal-only use of trusted files significantly reduces risk. However, if there is any possibility of external data entry or supply chain compromise, patching within your normal maintenance window is still prudent to avoid misconfigurations or future exposure.
This analysis is based on publicly available vulnerability data and CVSS metrics as of the publication date. Security assessments are time-sensitive; review vendor advisories and your own environment for the most current patch status and compatibility information. No exploit code or proof-of-concept details are provided. Risk scores are contextual; your organization's exposure depends on deployment architecture, data sources, and security controls. Always validate patches in a staging environment before production deployment. Source: NVD (public-domain), retrieved 2026-08-02. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2025-55644MEDIUMHeap Use-After-Free in GPAC MP4Box v2.4 DoS Vulnerability
- CVE-2025-55650MEDIUMHeap Use-After-Free in GPAC MP4Box v2.4 DoS Vulnerability
- CVE-2025-60466MEDIUMGPAC MP4Box Use-After-Free DoS Vulnerability
- CVE-2025-60471MEDIUMUse-After-Free in GPAC MP4Box Before 26.02.0 Denial of Service
- CVE-2026-0125HIGHAndroid VPU Race Condition Local Privilege Escalation
- CVE-2026-0137HIGHAndroid Edge TPU Use-After-Free Privilege Escalation
- CVE-2026-0143HIGHAndroid LWIS Use-After-Free Privilege Escalation (CVSS 7.8 HIGH)
- CVE-2026-10000HIGHChrome Sandbox Escape via Use-After-Free in Password Handling