NGINX Open Source and NGINX Plus have a vulnerability in the ngx_http_mp4_module module, which might allow an attacker to trigger a buffer over-read or over-write to the NGINX worker memory resulting in its termination or possibly code execution, using a specially crafted MP4 file. This issue affects NGINX Open Source and NGINX Plus if it is built with the ngx_http_mp4_module module and the mp4 directive is used in the configuration file. Additionally, the attack is possible only if an attacker can trigger the processing of a specially crafted MP4 file with the ngx_http_mp4_module module.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Security readout for executives and security teams
Plain-English summary
This vulnerability affects NGINX deployments that use the MP4 processing module. A crafted MP4 file can corrupt or read worker memory, causing worker termination and possibly code execution. Business risk is highest where users or partners can upload or trigger processing of MP4 files.
Executive priority
Prioritize remediation for public media services, upload portals, and edge systems running NGINX MP4 handling. The issue can crash worker processes and may allow code execution, but exploitation depends on a specific module and configuration.
Technical view
CVE-2026-32647 is a high-severity memory safety issue in ngx_http_mp4_module, described as buffer over-read or over-write in NGINX worker memory. Exploitation requires NGINX built with the module, the mp4 directive enabled, and attacker-triggered processing of a crafted MP4 file.
Likely exposure
Exposure appears limited to NGINX Open Source or NGINX Plus configurations using ngx_http_mp4_module with the mp4 directive. Static web servers without this module, without mp4 enabled, or without attacker-triggerable MP4 processing are less likely exposed.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. The CVSS vector lists local attack vector and low privileges, but the description centers on crafted MP4 processing. Treat internet-facing upload or media workflows as higher risk.
Researcher notes
Evidence is incomplete around exact fixed upstream versions in the supplied bundle. The affected data also appears internally inconsistent for NGINX Plus, listing releases while showing a default unaffected status. Use vendor advisories as the control source.
Mitigation direction
Review F5 advisory K000160366 for affected versions and fixed guidance.
Apply relevant Red Hat security errata where using Red Hat-packaged NGINX.
Disable the mp4 directive if MP4 pseudo-streaming is not required.
Avoid processing untrusted MP4 files through ngx_http_mp4_module.
Consider rebuilding without ngx_http_mp4_module where operationally feasible.
Validation and detection
Inventory NGINX instances and package sources across production and edge hosts.
Check whether NGINX was built with ngx_http_mp4_module.
Inspect configurations for active mp4 directives.
Identify routes or workflows that process uploaded or user-controlled MP4 files.
Confirm remediation against F5 and Red Hat advisory status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
3CVSS vectors
5Timeline events
2ADP providers
20Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
3 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.