CVE-2025-55642: GPAC MP4Box Floating Point Exception Denial of Service
GPAC MP4Box version 2.4 contains a flaw that can cause the application to crash when processing certain MP4 files. The vulnerability exists in code responsible for handling audio and video data during file writing operations. An attacker could craft a malicious MP4 file that, when opened in MP4Box, triggers a mathematical error leading to a denial of service. No data theft or file corruption occurs, but the crash prevents legitimate work with video files.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 6.5 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- Weaknesses (CWE)
- CWE-369
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-15 / 2026-06-17
NVD description (verbatim)
GPAC MP4Box v2.4 was discovered to contain a floating point exception in the avidmx_process function (isomedia/isom_write.c).
2 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2025-55642 is a floating point exception vulnerability in GPAC MP4Box v2.4, specifically within the avidmx_process function located in isomedia/isom_write.c. The flaw is classified as CWE-369 (Divide by Zero), a subset of improper numeric handling. The vulnerability is triggered during MP4 file processing when the application encounters malformed or specially crafted input that causes a division by zero or equivalent floating point operation to fail. The attack vector is network-based with low complexity and requires user interaction to open a malicious file, but no authentication or special privileges are needed.
Business impact
For organizations relying on MP4Box for video transcoding, format conversion, or media pipeline automation, this vulnerability introduces availability risk. A single malicious file could halt batch processing workflows, delay content publishing timelines, or crash unattended encoding services. The impact is primarily operational rather than confidential or integrity-focused—no user data is at risk, but service disruption is the concern. Media production, broadcast, and streaming companies should assess whether MP4Box is embedded in critical automation paths.
Affected systems
GPAC MP4Box version 2.4 is confirmed affected. Users of earlier or later versions should verify against official GPAC release notes and security advisories to determine the exact affected and patched versions. MP4Box is often integrated into third-party media software, container applications, and custom video processing pipelines; check your toolchain dependencies.
Exploitability
Exploitation is straightforward: an attacker must craft a malicious MP4 file and deliver it to a target user or system for processing. Since user interaction is required (opening or processing the file), this is not a wormable or automatic threat. However, in automated environments where MP4Box processes files from untrusted sources—such as user-uploaded content platforms or public APIs—the barrier to exploitation is low. No exploit code appears to be publicly documented, but the simplicity of the flaw makes weaponization trivial.
Remediation
Update GPAC MP4Box to a patched version released after this vulnerability disclosure. Verify the specific patch version against official GPAC release notes and security advisories. Until patching is complete, restrict file processing to trusted sources and implement file validation before feeding content to MP4Box. Consider running MP4Box in isolated, containerized environments to limit collateral impact from crashes.
Patch guidance
Check the official GPAC project repository and release notes for version numbers that address CVE-2025-55642. The vulnerability was disclosed on June 15, 2026 with updates through June 17, 2026; patched versions should be available shortly after. Test patches in non-production environments to ensure no regression in encoding or transcoding output quality before deployment.
Detection guidance
Monitor for unexpected crashes or exit codes from MP4Box processes, particularly when handling user-supplied or external video files. Log file processing attempts and correlate crashes with specific input files to identify patterns. If MP4Box is deployed in a container, watch for frequent restarts. File integrity monitoring on input directories may help identify suspicious files before processing. Network-based detection is limited unless you can inspect file uploads for MP4 malformation signatures.
Why prioritize this
This vulnerability scores CVSS 6.5 (MEDIUM) due to its network accessibility and ease of exploitation offset by the lack of direct data compromise and requirement for user interaction. Prioritization should reflect your use of MP4Box: critical if it processes untrusted user-uploaded content or runs in automated pipelines exposed to external input; lower priority if usage is internal-only and file sources are strictly controlled.
Risk score, explained
The CVSS 3.1 score of 6.5 reflects an attack vector that is network-accessible (AV:N) with low attack complexity (AC:L) and no privilege or authentication requirements (PR:N, UI:R). User interaction is required, reducing the attack surface. The impact is limited to availability (A:H), with no confidentiality or integrity compromise (C:N, I:N). This places it in the MEDIUM severity band—a credible operational risk but not a critical system breach vector.
Frequently asked questions
Does this vulnerability allow an attacker to steal data or corrupt files?
No. CVE-2025-55642 causes a denial of service through application crash only. There is no data exfiltration, file corruption, or privilege escalation. The impact is strictly availability.
Can this be exploited without user interaction?
No, a user or process must attempt to open or process a malicious MP4 file with MP4Box for the vulnerability to trigger. Automated systems that accept external files are at higher risk than isolated, manual workflows.
What versions of GPAC are affected?
GPAC MP4Box v2.4 is confirmed affected. Consult official GPAC release notes and security advisories to determine which other versions are vulnerable and which patches resolve the issue.
Is there a public exploit?
No public exploit has been documented in the provided source data. However, the simplicity of a floating point exception means that proof-of-concept code could emerge quickly once the vulnerability is widely known.
This analysis is based on vulnerability disclosure data current as of June 17, 2026. Specific patch version numbers, affected software versions, and KEV status should be verified against official vendor advisories and CISA resources. This explainer provides general guidance and does not constitute legal, compliance, or procurement advice. Organizations should conduct risk assessments specific to their environment and threat model. Source: NVD (public-domain), retrieved 2026-07-23. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2025-70100MEDIUMlwext4 Divide-by-Zero Denial of Service (MEDIUM)
- CVE-2026-46161MEDIUMLinux Kernel RAID10 Divide-by-Zero Denial of Service
- CVE-2026-46184MEDIUMLinux ua101 USB Audio Driver Division-by-Zero Denial-of-Service
- CVE-2026-10201LOWAssimp FBX Divide-by-Zero Denial of Service
- CVE-2026-37232HIGHOpenAirInterface5G KPM Division-by-Zero DoS Vulnerability
- CVE-2025-55641MEDIUMNULL Pointer Dereference in GPAC MP4Box v2.4 Denial of Service
- CVE-2025-55643MEDIUMGPAC MP4Box NULL Pointer DoS Vulnerability
- CVE-2025-55644MEDIUMHeap Use-After-Free in GPAC MP4Box v2.4 DoS Vulnerability