Visualização normal

Antes de ontemStream principal
  • ✇Security Affairs
  • CVE-2026-42533: Critical NGINX Bug Could Turn HTTP Requests Into Server Takeovers Pierluigi Paganini
    F5 fixes critical nginx flaw CVE-2026-42533 that can crash servers and, in some cases, allow remote code execution through crafted HTTP requests. F5 released patches for a critical nginx vulnerability, tracked as CVE-2026-42533 (CVSS score of 9.2), that can allow an unauthenticated attacker to trigger a heap buffer overflow using specially crafted HTTP requests. “heap buffer overflow might occur in a worker process when using the map directive with regex matching if the map variable was
     

CVE-2026-42533: Critical NGINX Bug Could Turn HTTP Requests Into Server Takeovers

20 de Julho de 2026, 06:50

F5 fixes critical nginx flaw CVE-2026-42533 that can crash servers and, in some cases, allow remote code execution through crafted HTTP requests.

F5 released patches for a critical nginx vulnerability, tracked as CVE-2026-42533 (CVSS score of 9.2), that can allow an unauthenticated attacker to trigger a heap buffer overflow using specially crafted HTTP requests.

“heap buffer overflow might occur in a worker process when using the map directive with regex matching if the map variable was included in a string expression after a capture affected by this map; a similar issue might happen when using a non-cacheable variable in a string expression (CVE-2026-42533).” reads the advisory.

CVE-2026-42533 affects NGINX Plus and Open Source when specific regex-based map configurations are used. An unauthenticated attacker can send crafted HTTP requests to trigger a heap buffer overflow, causing crashes or denial of service. In certain conditions, especially if ASLR is disabled or bypassed, the flaw may also allow remote code execution. The issue affects only the data plane, not the control plane.

The vulnerability affects NGINX versions from 0.9.6 through 1.31.2. F5 fixed the issue in NGINX 1.30.4, 1.31.3 and NGINX Plus 37.0.3.1. The flaw impacts only the data plane and does not expose the NGINX control plane.

As a temporary workaround, affected regex-based map configurations can be modified to use named captures instead of numbered captures, but this does not provide complete protection.

The researchers Mufeed VH of Winfunc Research and Maxim Dounin discovered the vulnerability.

Security researcher Stan Shaw (cyberstan) reported that CVE-2026-42533 may have a higher impact than initially described by F5. While F5 highlights denial-of-service risks, Shaw believes the flaw could also help attackers bypass ASLR protections and achieve remote code execution under certain conditions. He has not released exploit details or a proof-of-concept yet.

Shaw released a static scanner that identifies vulnerable NGINX configurations without exploiting the flaw. The tool checks include files, analyzes directive relationships, and detects exploitable patterns. Shaw is delaying publication of the proof-of-concept and technical exploitation details to give organizations time to patch, noting that similar NGINX flaws were exploited soon after PoCs became public.

Follow me on Twitter: @securityaffairs and Facebook and Mastodon

Pierluigi Paganini

(SecurityAffairs – hacking, F5)

  • ✇Firewall Daily – The Cyber Express
  • CVE-2026-42533 Exposes Critical Pre-Auth nginx RCE Flaw Ashish Khaitan
    A newly disclosed security flaw, CVE-2026-42533, has revealed a critical Pre-Auth nginx vulnerability that could allow attackers to achieve reliable RCE (remote code execution) without authentication. The issue affects nginx versions 0.9.6 through 1.30.3 (stable) and 1.31.2 (mainline), while patched releases include 1.30.4 and 1.31.3. Affected NGINX Plus versions include R33-R36 (fixed in R36 P7) and 37.0.0.1-37.0.2.1 (fixed in 37.0.3.1).  According to the disclosure, the vulnerability stems
     

CVE-2026-42533 Exposes Critical Pre-Auth nginx RCE Flaw

CVE-2026-42533

A newly disclosed security flaw, CVE-2026-42533, has revealed a critical Pre-Auth nginx vulnerability that could allow attackers to achieve reliable RCE (remote code execution) without authentication. The issue affects nginx versions 0.9.6 through 1.30.3 (stable) and 1.31.2 (mainline), while patched releases include 1.30.4 and 1.31.3. Affected NGINX Plus versions include R33-R36 (fixed in R36 P7) and 37.0.0.1-37.0.2.1 (fixed in 37.0.3.1).  According to the disclosure, the vulnerability stems from a missing save-and-restore mechanism for PCRE capture state within nginx's two-pass script evaluation engine. The flaw enables attackers to trigger a heap buffer overflow with attacker-controlled content and length, while also exposing heap pointers through an information leak that can defeat Address Space Layout Randomization (ASLR). Chaining both primitives enables reliable Pre-Auth nginx RCE. 

CVE-2026-42533 Impacts Multiple Configurations 

The advisory warns that deployments using map directives with regex patterns alongside regex capture sources, including location, server_name, rewrite, or if blocks, may be vulnerable. The issue depends on evaluation order, where regex capture references, such as $1 or named groups, are processed before a regex map variable.  Affected directives include proxy_set_header, proxy_method, proxy_pass, fastcgi_param, uwsgi_param, scgi_param, grpc_set_header, return, add_header, rewrite, set, root, alias, and access_log, among others. Both HTTP and stream modules are affected, and the vulnerable capture and map variables do not need to exist within the same directive. 

Technical Root Cause

The researcher explained that nginx evaluates expressions in two stages: a length calculation (LEN) pass followed by a value (VALUE) pass. During execution, regex map evaluation overwrites shared capture data stored in the request object. As a result, the LEN pass and VALUE pass can calculate different capture sizes, causing either a heap overflow or an information leak depending on the relative capture lengths.  The disclosure states that attackers can control both the overflow size and leaked data using ordinary HTTP requests, including request URIs, headers, and bodies. No credentials, client certificates, or unusual configuration beyond the vulnerable pattern are required.  Testing reportedly achieved 10 out of 10 successful exploitations on Ubuntu 24.04 using glibc 2.39 with ASLR enabled.

Mitigation and Disclosure

The researcher said recent fixes for CVE-2026-42945, CVE-2026-9256, CVE-2026-42055, and CVE-2026-48142 do not address CVE-2026-42533. Administrators are advised to upgrade immediately to nginx 1.30.4, 1.31.3, or the corresponding patched NGINX Plus releases.  Until systems are updated, defenders should audit configurations that combine regex captures with regex map variables in the same evaluation path. The researcher also released a static configuration scanner that identifies vulnerable configurations without exploiting them.  The initial report was submitted to F5 SIRT on May 17, 2026, with follow-up analyses covering additional variants, including cross-directive triggering and named capture clobbering. While a proof-of-concept exploit exists, the researcher said it will be withheld until users have sufficient time to apply patches, citing concerns over rapid exploitation following previous nginx vulnerability disclosures. 
  • ✇Security Affairs
  • F5 Patches Critical NGINX Vulnerabilities Enabling Unauthenticated Code Execution Pierluigi Paganini
    F5 released emergency updates for critical NGINX flaws (CVE-2026-42530, CVE-2026-42055) that could enable unauthenticated code execution. F5 has issued out-of-band patches for multiple NGINX vulnerabilities, including two critical flaws, respectively tracked as CVE-2026-42530 and CVE-2026-42055 (CVSS 9.2). The bugs affect HTTP modules and can be exploited remotely without authentication to trigger memory corruption, potentially causing service restarts or enabling arbitrary code execution.
     

F5 Patches Critical NGINX Vulnerabilities Enabling Unauthenticated Code Execution

18 de Junho de 2026, 11:07

F5 released emergency updates for critical NGINX flaws (CVE-2026-42530, CVE-2026-42055) that could enable unauthenticated code execution.

F5 has issued out-of-band patches for multiple NGINX vulnerabilities, including two critical flaws, respectively tracked as CVE-2026-42530 and CVE-2026-42055 (CVSS 9.2). The bugs affect HTTP modules and can be exploited remotely without authentication to trigger memory corruption, potentially causing service restarts or enabling arbitrary code execution.

The flaw CVE-2026-42530 (CVSS score of 9.2) is a critical Use-After-Free vulnerability in the ngx_http_v3_module of NGINX Open Source. When HTTP/3 QUIC support is enabled, a remote unauthenticated attacker can exploit a specially crafted HTTP/3 session to reopen a QPACK encoder stream, causing memory corruption in the NGINX worker process. Successful exploitation may lead to service disruption and worker process restarts, and under certain conditions, such as when ASLR is disabled or bypassed, could allow arbitrary code execution.

“NGINX Open Source has a vulnerability in the ngx_http_v3_module module. When NGINX Open Source is configured to use the HTTP/3 QUIC module, a remote unauthenticated attacker along with conditions beyond their control can use a specially crafted HTTP/3 session to reopen a QPACK encoder stream. This may cause a Use-After-Free in the NGINX worker process, leading to a restart. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. (CVE-2026-42530)” reads the advisory. “This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution. There is no control plane exposure; this is a data plane issue only.”

The second flaw, tracked as CVE-2026-42055 (CVSS score of 9.2), is a critical heap-based buffer overflow vulnerability affecting the ngx_http_proxy_v2_module and ngx_http_grpc_module in NGINX Open Source and Plus. Under specific configurations involving HTTP/2 proxying, disabled header validation, and large header buffers, a remote unauthenticated attacker can send specially crafted oversized headers to trigger memory corruption in the worker process. Successful exploitation may cause service disruption and worker process restarts, and in environments where ASLR is disabled or bypassed, could potentially lead to arbitrary code execution.

“This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution; however, exploitation requires non-default configuration to be present.” states the advisory.

The vulnerability can lead to DoS or potential code execution, but only in non-default configurations. Exploitation requires HTTP/2 proxying, disabled header validation, and unusually large header buffers. Default deployments are not affected, and the issue impacts only the data plane, not the control plane.

F5 has released security updates for NGINX Plus, NGINX Open Source, and NGINX Gateway Fabric to fix the recently disclosed vulnerabilities.

The company also addressed two high-severity vulnerabilities, tracked as CVE-2026-11311 and CVE-2026-50107, in NGINX Gateway Fabric that could allow authenticated attackers to inject arbitrary NGINX configuration directives.

At this time, there is no news of attacks in the wild exploiting one of the vulnerabilities.

Follow me on Twitter: @securityaffairs and Facebook and Mastodon

Pierluigi Paganini

(SecurityAffairs – hacking, F5)

Hackers Actively Exploit ‘Nginx Rift’ Vulnerability Affecting NGINX, F5 Products

Hackers are actively exploiting the Nginx Rift vulnerability affecting NGINX and F5 products, exposing servers to denial-of-service attacks.
❌
❌