Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-27784: CWE-190 Integer Overflow or Wraparound in F5 NGINX Open Source

0
High
VulnerabilityCVE-2026-27784cvecve-2026-27784cwe-190
Published: Tue Mar 24 2026 (03/24/2026, 14:13:25 UTC)
Source: CVE Database V5
Vendor/Project: F5
Product: NGINX Open Source

Description

CVE-2026-27784 is a high-severity integer overflow vulnerability affecting the 32-bit builds of F5's NGINX Open Source when compiled with the ngx_http_mp4_module and the mp4 directive enabled. An attacker can exploit this by sending a specially crafted MP4 file, causing the module to over-read or overwrite memory, potentially crashing the NGINX worker process or leading to further compromise. The vulnerability requires local privileges or limited privileges (PR:L) and no user interaction, with low attack complexity. It only affects specific versions (1. 29. 0 and 1. 1. 19) on 32-bit systems, which are less common today. No known exploits are currently reported in the wild. Organizations using 32-bit NGINX Open Source with the mp4 module enabled should prioritize patching or mitigating this issue to prevent service disruption or potential escalation of privileges.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/31/2026, 20:19:19 UTC

Technical Analysis

CVE-2026-27784 is an integer overflow or wraparound vulnerability classified under CWE-190, found in the ngx_http_mp4_module of the 32-bit implementation of F5's NGINX Open Source. This module handles MP4 streaming and processing. The flaw arises when processing specially crafted MP4 files, causing the module to miscalculate buffer sizes or offsets due to integer overflow, leading to out-of-bounds memory access. This can result in over-reading or overwriting the memory space allocated to NGINX worker processes, potentially causing worker termination (denial of service) or enabling an attacker to corrupt memory in a way that could lead to arbitrary code execution or privilege escalation. The vulnerability is limited to 32-bit builds where the mp4 directive is enabled in the configuration, and the affected versions are 1.29.0 and 1.1.19. Exploitation requires the attacker to have the ability to trigger processing of a malicious MP4 file, which implies some level of access to the HTTP service. The CVSS v3.1 score is 7.8, reflecting high impact on confidentiality, integrity, and availability, with low attack complexity and limited privileges required but no user interaction. No patches were linked in the provided data, and no known exploits have been observed in the wild as of the publication date.

Potential Impact

The vulnerability can lead to denial of service by crashing NGINX worker processes, disrupting web services relying on MP4 streaming. More critically, memory corruption could allow attackers to execute arbitrary code or escalate privileges within the NGINX process context, potentially compromising the underlying server and network. Organizations using 32-bit NGINX Open Source with the mp4 module enabled are at risk of service outages and data breaches. Given the high confidentiality, integrity, and availability impacts, exploitation could affect sensitive data confidentiality and service reliability. Although 32-bit deployments are less common, legacy systems or embedded devices may still be vulnerable. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits over time.

Mitigation Recommendations

Organizations should first verify if they are running 32-bit versions of NGINX Open Source with the ngx_http_mp4_module enabled and the mp4 directive configured. If so, immediate mitigation includes disabling the mp4 module or the mp4 directive to prevent processing of MP4 files until a patch is available. Upgrading to a 64-bit version of NGINX Open Source, which is not affected, is strongly recommended. Monitoring HTTP logs for unusual MP4 file requests and implementing strict input validation or filtering on MP4 content can reduce exposure. Employing runtime protections such as memory safety tools or sandboxing NGINX worker processes may limit exploitation impact. Regularly check for official patches or updates from F5 and apply them promptly once released. Additionally, restrict access to the HTTP service to trusted users and networks to reduce the attack surface.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
f5
Date Reserved
2026-03-18T16:06:38.416Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69c2a3a3f4197a8e3b3ed93e

Added to database: 3/24/2026, 2:45:55 PM

Last enriched: 3/31/2026, 8:19:19 PM

Last updated: 4/28/2026, 11:28:15 AM

Views: 65

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses