CVE-2026-32647
7.8F5 · NGINX Open Source and NGINX Plus
A buffer handling vulnerability exists in the ngx_http_mp4_module of NGINX, which may allow an attacker to cause memory corruption or remote code execution via a specially crafted MP4 file.
Executive summary
A critical memory corruption vulnerability in the NGINX MP4 module could allow an attacker to trigger worker process termination or achieve arbitrary code execution.
Vulnerability
This vulnerability involves a buffer over-read or over-write condition within the ngx_http_mp4_module, triggered when the server processes a maliciously crafted MP4 file. The vulnerability is exploitable by a local authenticated attacker, requiring the mp4 directive to be enabled in the NGINX configuration.
Business impact
The potential for arbitrary code execution poses a severe risk to infrastructure integrity, as a successful exploit could grant an attacker control over the NGINX worker process. Given the CVSS score of 7.8, this vulnerability represents a high-severity threat that could lead to service disruption or unauthorized system access, necessitating prompt remediation to prevent compromise of web-facing assets.
Remediation
Immediate Action: Update NGINX Open Source or NGINX Plus to the versions specified in the F5 security advisory (K000160366) to ensure the ngx_http_mp4_module is patched.
Proactive Monitoring: Review NGINX worker process logs for frequent, unexplained crashes or segmentation faults, which may indicate attempted exploitation of the buffer handling flaw.
Compensating Controls: If patching is not immediately feasible, disable the mp4 module in the NGINX configuration file if it is not strictly required for business operations.
Exploitation status
Public Exploit Available: Unknown.
Analyst recommendation
Organizations utilizing NGINX with the mp4 module enabled must prioritize this update. Because this vulnerability allows for process termination or code execution, it represents a significant security gap. Administrators should verify their current versions against the F5 advisory and apply the necessary patches immediately to mitigate the risk of unauthorized access or service denial.
More F5 CVEs
Sources
Originally found and disclosed by F5 acknowledges Xint Code and Pavel Kohout (Aisle Research) for bringing this issue to our attention and following the h, per the CVE Program record.