The 32-bit implementation of NGINX Open Source has a vulnerability in the ngx_http_mp4_module module, which might allow an attacker to over-read or over-write NGINX worker memory resulting in its termination, using a specially crafted MP4 file. The issue only affects 32-bit NGINX Open Source 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 issue affects a narrow NGINX Open Source setup: 32-bit builds using the MP4 module with the mp4 directive enabled. A crafted MP4 can corrupt or over-read worker memory and terminate a worker. Business risk is highest for sites that process or serve untrusted MP4 files through affected NGINX configurations.
Executive priority
Prioritize verification for media-serving environments and legacy 32-bit systems. The affected configuration is specific, but impact is high where present because crafted media can affect NGINX worker memory and availability. Treat remediation as urgent for internet-facing or user-uploaded MP4 workflows.
Technical view
CVE-2026-27784 is a CWE-190 integer overflow in the 32-bit implementation of ngx_http_mp4_module. Exploitation requires an attacker to trigger processing of a specially crafted MP4 file by the module. The CVSS 4.0 score is 8.5, with high confidentiality, integrity, and availability impact stated in the record.
Likely exposure
Exposure appears limited to 32-bit NGINX Open Source builds compiled with ngx_http_mp4_module, with the mp4 directive enabled, and reachable MP4 processing paths. 64-bit builds or configurations not using the module are not described as affected in the provided sources.
Exploitation context
The bundle does not cite active exploitation, and KEV is false. Sources describe a crafted MP4 triggering worker memory over-read or over-write, potentially terminating the worker. The record’s CVSS vector indicates local access and low privileges, but operational exposure depends on how MP4 files reach NGINX.
Researcher notes
Do not generalize this to all NGINX deployments. The provided scope requires 32-bit NGINX Open Source, ngx_http_mp4_module, the mp4 directive, and attacker-triggered MP4 processing. Evidence in the bundle does not establish public exploitation or affected end-of-technical-support versions.
Mitigation direction
Check F5 and Red Hat advisories for applicable fixed packages or vendor guidance.
Disable the mp4 directive where MP4 pseudo-streaming is not required.
Avoid affected 32-bit NGINX Open Source builds where feasible.
Restrict untrusted MP4 upload or processing paths until remediation is confirmed.
Monitor NGINX worker crashes and abnormal MP4 request patterns.
Validation and detection
Inventory NGINX Open Source deployments and confirm whether any are 32-bit builds.
Review NGINX build options for ngx_http_mp4_module presence.
Review configuration for active mp4 directives.
Map whether external users can cause MP4 files to be processed by NGINX.
Compare installed packages 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-190: 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.
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-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.