Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-60496 Overview
CVE-2025-60496 is a Floating-Point Exception (FPE) vulnerability in the reframer_send_packet function located in /filters/reframer.c of the GPAC Project. The flaw affects MP4Box builds before version 2.5. An attacker can trigger the exception by supplying a crafted MP4 file, resulting in a Denial of Service (DoS) condition on the processing application. The issue stems from a division operation that uses an unchecked zero denominator in the extraction logic.
Critical Impact
Processing a malicious MP4 file causes MP4Box to crash via a divide-by-zero exception, breaking any automated media pipeline that ingests untrusted content.
Affected Products
- GPAC Project versions before 2.5
- MP4Box command-line utility bundled with GPAC
- Applications and services embedding the GPAC reframer filter
Discovery Timeline
- 2026-10-20 - CVE-2025-60496 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2025-60496
Vulnerability Analysis
The vulnerability resides in the GPAC reframer filter, which handles segmentation and extraction of media streams during MP4 processing. When MP4Box executes in EXTRACT_SAP or EXTRACT_SIZE extraction mode, the filter copies the current end timestamp into the start timestamp as a rational number consisting of a numerator and denominator. If the denominator (den) is zero after this assignment, subsequent arithmetic performs an integer division by zero. The resulting Floating-Point Exception terminates the process. The impact is limited to availability, but automated transcoding, streaming, or indexing pipelines that ingest attacker-supplied MP4 files will fail each time a crafted sample is parsed.
Root Cause
The root cause is missing input validation on the cur_start.den field after it is copied from cur_end. The code path does not verify that the denominator is non-zero before downstream calculations rely on it. This is an Input Validation Error that manifests as a Divide-by-Zero Denial of Service condition.
Attack Vector
An attacker crafts an MP4 file whose structure causes the reframer to assign a zero denominator during SAP or size-based extraction. The victim processes the file with a vulnerable MP4Box binary or any application linking the GPAC reframer filter. No authentication is required, and exploitation does not need network access beyond delivering the file to the target processing system.
// Patch from src/filters/reframer.c - commit f03c946aae129980f0426d4cbae9746d0536fee6
if ((ctx->extract_mode==EXTRACT_SAP) || (ctx->extract_mode==EXTRACT_SIZE)) {
ctx->cur_start = ctx->cur_end;
+ if (!ctx->cur_start.den) ctx->cur_start.den = 1;
ctx->min_ts_computed = 0;
ctx->min_ts_scale = 0;
ctx->file_idx++;
Source: GPAC commit f03c946. The fix forces cur_start.den to 1 when it would otherwise be zero, eliminating the divide-by-zero path.
Detection Methods for CVE-2025-60496
Indicators of Compromise
- Unexpected SIGFPE crashes or core dumps generated by MP4Box or GPAC-linked processes
- Media processing jobs terminating with non-zero exit codes immediately after loading an MP4 file
- Repeated submissions of malformed MP4 files from a single untrusted source to transcoding or ingestion endpoints
Detection Strategies
- Audit installed GPAC packages and binary versions to identify builds prior to 2.5
- Enable crash reporting on media processing hosts and correlate SIGFPE events with the MP4Box process name
- Review MP4 ingestion logs for files that failed parsing in the reframer filter stages
Monitoring Recommendations
- Monitor process termination telemetry for GPAC utilities on Linux and Windows media servers
- Alert on anomalous spikes in failed media conversion jobs tied to specific uploaded files
- Track filesystem writes of core dumps or Windows Error Reporting entries referencing GPAC modules
How to Mitigate CVE-2025-60496
Immediate Actions Required
- Upgrade GPAC and MP4Box to version 2.5 or later, which includes the fix from commit f03c946
- Restrict upload of untrusted MP4 files to media processing services pending patch deployment
- Run MP4Box and GPAC-based workers under isolated service accounts with automatic restart to limit DoS impact
Patch Information
The fix is implemented in the upstream GPAC repository via commit f03c946aae129980f0426d4cbae9746d0536fee6, which resolves GitHub Issue #3334. The patch guards the cur_start.den denominator and sets it to 1 when zero. Users should install GPAC 2.5 or later, or rebuild from a source tree that includes the referenced commit. Additional context is available on the OpenWall oss-security list and the proof-of-concept README.
Workarounds
- Validate incoming MP4 files with a secondary parser before passing them to MP4Box
- Avoid using EXTRACT_SAP and EXTRACT_SIZE extraction modes on untrusted input until patched
- Sandbox MP4Box execution with resource limits and crash recovery (for example, systemd service units with Restart=on-failure)
# Verify installed GPAC version and update on Debian/Ubuntu
MP4Box -version 2>&1 | head -n 1
sudo apt-get update && sudo apt-get install --only-upgrade gpac
# Build from source with the fix applied
git clone https://github.com/gpac/gpac.git
cd gpac && git checkout v2.5
./configure && make -j$(nproc) && sudo make install
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

