Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oracle · 3h CISA Warns of 4 Exploited Flaws Linked to Ransomware, Cryptomining, and LLMjacking Attacks · 3h PHP Warns of Critical Security Flaws Affecting All Supported Versions, Fixes Coming November 19 · 6h 10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers · 16h F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE · 17h CVE-2026-123633 and CVE-2026-123007: Critical NGINX HTTP/2 Vulnerabilities · 18h Critical Apache Roller RCE Flaw Under Active Exploitation, No Authentication Required · 18h Java4Shell Flaw Threatens Global Enterprises, Java Application Ecosystem · 18h How Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938) · 20h Vulnerabilities in LMS software · 22h Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oracle · 3h CISA Warns of 4 Exploited Flaws Linked to Ransomware, Cryptomining, and LLMjacking Attacks · 3h PHP Warns of Critical Security Flaws Affecting All Supported Versions, Fixes Coming November 19 · 6h 10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers · 16h F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE · 17h CVE-2026-123633 and CVE-2026-123007: Critical NGINX HTTP/2 Vulnerabilities · 18h Critical Apache Roller RCE Flaw Under Active Exploitation, No Authentication Required · 18h Java4Shell Flaw Threatens Global Enterprises, Java Application Ecosystem · 18h How Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938) · 20h Vulnerabilities in LMS software · 22h
🛡️
ACyber Sentinel Security Assessment Team
← Back to feed
⚡ Intelligence Report

F5 Addresses Multiple NGINX Vulnerabilities in October Security Update

F5 Addresses Multiple NGINX Vulnerabilities in October Security Update


F5 and the NGINX project released security fixes on October 14, 2026, addressing five vulnerabilities in NGINX Open Source and NGINX Plus. The issues affect memory handling, HTTP/3 request processing and TLS session security. Three of the vulnerabilities have been assigned a CVSS 4.0 score of 9.2 by F5, highlighting the potential impact under specific conditions.

NGINX is widely used as a web server, reverse proxy, load balancer and application traffic gateway. A vulnerability in these components can affect more than website availability: depending on the configuration and the flaw, it can also expose applications to request manipulation or compromise of a worker process.

The important distinction is that these vulnerabilities do not affect every installation in the same way. Some require particular NGINX directives or features to be enabled. Administrators should therefore assess both the installed version and the active configuration before deciding their response.

Five vulnerabilities to know

The October 14 release fixes five vulnerabilities in NGINX Open Source.

1. CVE-2026-15176 — Buffer overflow involving alias and rewrite

This vulnerability occurs when a location is configured with the alias directive alongside rewrite and a set or return directive referencing $request_filename. A similar condition can arise when the variable is used in an access-log format.

A crafted HTTP request can trigger a heap buffer overflow in an NGINX worker process, potentially causing a denial-of-service condition. Code execution may also be possible when Address Space Layout Randomization (ASLR) is disabled or can be bypassed.

F5 rates this vulnerability CVSS 4.0: 9.2 (Critical).

2. CVE-2026-93479 — Buffer overflow in script evaluation

This vulnerability affects NGINX when evaluating string expressions involving variables, particularly in configurations using regular-expression matching with the map directive.

Under the relevant conditions, an attacker can trigger a buffer overflow in the worker process. The potential consequences include service disruption and, under specific circumstances, code execution.

F5 assigns this vulnerability a CVSS 4.0 score of 9.2 (Critical).

3. CVE-2026-97205 — Use-after-free involving asynchronous file I/O

This issue affects configurations where asynchronous file I/O (AIO) is enabled and a Server Side Includes (SSI) page uses the include virtual command.

A use-after-free condition can corrupt worker-process memory when specially crafted requests trigger the vulnerable code path. This may result in a worker crash or, under specific conditions, code execution.

F5 assigns this vulnerability a CVSS 4.0 score of 9.2 (Critical). The configuration requirements are important: deployments that do not use the affected combination may not be exposed to this particular attack path.

4. CVE-2026-95101 — HTTP/3 request-body injection

This vulnerability affects the ngx_http_v3_module when HTTP/3 is enabled and the proxy_request_buffering directive is on.

An unauthenticated attacker may be able to inject data into a proxied request. Depending on how the application processes the request, this could affect request integrity and the handling of traffic forwarded to upstream services.

The reported impact is request injection rather than the memory-corruption behaviour associated with the first three vulnerabilities.

5. CVE-2026-97629 — TLS session forgery

This vulnerability concerns TLS session tickets and key rotation. A weakness in session-ticket handling can allow session forgery under the conditions described in the security advisory.

Because TLS session management is part of the security boundary between clients and services, administrators should assess this issue alongside the memory-safety and HTTP/3 flaws rather than focusing exclusively on the highest CVSS scores.

Affected and fixed versions

For NGINX Open Source, the October 14 release provides fixes for all five vulnerabilities in the following versions.

NGINX Open Source

  • Stable branch: upgrade to 1.30.6 or later in that branch.
  • Mainline branch: upgrade to 1.31.7 or later in that branch.

NGINX Plus

  • Release 37.0: F5 lists 37.0.5.1 as a fix for the three critical memory-safety vulnerabilities.
  • Release 37.1: F5 lists 37.1.0.1 as a fix for those three vulnerabilities.

Important: these NGINX Plus versions should not automatically be assumed to resolve every issue in the advisory across every branch. Confirm the exact release and fix status against the individual F5 advisory before upgrading.

Other F5 products to check

The security notification also requires administrators to assess other products that incorporate NGINX components. Depending on the product and the specific vulnerability, this includes:

  • NGINX Ingress Controller
  • NGINX Gateway Fabric
  • NGINX Instance Manager
  • F5 WAF for NGINX
  • F5 DoS for NGINX

For example, F5 lists NGINX Gateway Fabric versions before 2.8.0 and NGINX Instance Manager versions before 2.24.0 as affected by at least one vulnerability in this update. NGINX Ingress Controller and the security products have their own version-specific requirements.

Do not apply the NGINX Open Source version numbers directly to these products. Check their respective F5 product advisories and supported upgrade paths.

What security teams should do now

Start with an inventory of externally exposed NGINX instances, reverse proxies, ingress controllers and application gateways. Include both self-managed installations and products supplied through vendor packages or container images.

Next, verify the exact version and review the relevant configuration. Pay particular attention to the alias, rewrite, map, AIO, SSI, HTTP/3 and TLS session-ticket settings. These checks help identify which vulnerabilities may be reachable in your environment.

Prioritise the three memory-safety vulnerabilities because of their potential for worker-process crashes and conditional code execution. However, do not leave the HTTP/3 request-injection and TLS session-forgery issues unaddressed simply because their impacts differ.

Where a patch cannot be deployed immediately, follow the mitigation instructions in the applicable F5 advisory. Configuration changes may reduce exposure, but they should not be treated as a substitute for upgrading to a fixed version.

Final takeaway

This update is a reminder that a widely deployed web-serving component can have several distinct security weaknesses discovered and fixed at the same time. The highest-risk issues involve memory corruption, but request integrity and TLS session security also deserve attention.

For security teams, the next step is straightforward: identify affected NGINX deployments, validate their configuration, confirm the appropriate fixed release and track remediation to completion.

Referenced Vulnerabilities

CVE-2026-102764 CVSS 9.8 CRITICAL Analyzed
CVE-2026-102764 - BeyondTrust Remote Support Authentication Bypass by Spoofing Vulnerability - [Actively Exploited]
The vulnerability exists within internal components of BeyondTrust’s Remote Support product. The components did not adequately validate the origin of the messages it received. Under the right conditions, this could allow an attacker to perform file operations on the appliance.
CVE-2026-97629 CVSS 8.3 HIGH Awaiting Analysis
CVE-2026-97629 - NGINX ngx_http_ssl_module vulnerability
Description When NGINX Plus or NGINX Open Source is configured with ssl_session_cache shared:name:size without an explicit ssl_session_ticket_key file directives to automatically rotate SSL session ticket keys, a remote unauthenticated attacker is able to forge client SSL sessions in a non-deterministic manner that is beyond the attacker's control. An attacker could leverage this vulnerability to bypass verification of client certificates. Impact This vulnerability can lead to the exposure of resources or functionality to unintended actors, possibly providing attackers with access to sensitive information. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
CVE-2026-97205 CVSS 9.2 CRITICAL Awaiting Analysis
CVE-2026-97205 - NGINX ngx_http_core_module vulnerability
NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_core_module module. When asynchronous file I/O (AIO) is enabled in certain configurations, processing a Server Side Includes (SSI) page containing “include virtual” commands may trigger a Use-After-Free (UAF) in the NGINX worker process. This may cause memory corruption or a worker process crash. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system, corrupt its memory, or possibly trigger code execution. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
CVE-2026-95101 CVSS 6.9 MEDIUM Awaiting Analysis
CVE-2026-95101 - NGINX ngx_http_v3_module vulnerability
Description NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_v3_module module. When using HTTP/3 with proxy_request_buffering on directive, an unauthenticated attacker may be able to inject data in the proxied request. Impact This vulnerability may allow remote attackers to inject data in the proxied request.  There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
CVE-2026-93479 CVSS 9.2 CRITICAL Awaiting Analysis
CVE-2026-93479 - NGINX map directive and regex matching vulnerability
A vulnerability exists in NGINX Plus and NGINX Open Source when a map directive uses regex matching and the root directive or access log format references the map's regex capture variables before referencing the map output variable. Alternatively, the same result could be achieved by using a non-cacheable variable in a string expression under certain conditions. An unauthenticated attacker along with conditions beyond their control can exploit this vulnerability by sending crafted HTTP requests. This may cause a heap buffer overflow 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. Impact:  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. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
CVE-2026-15176 CVSS 9.2 CRITICAL Awaiting Analysis
CVE-2026-15176 - NGINX ngx_http_core_module vulnerability
A vulnerability exists in NGINX Plus and NGINX Open Source when a location is configured that uses the alias directive together with rewrite and a set or return directive referencing the $request_filename variable. Alternatively, the same result could be achieved when the $request_filename variable is used in an access log format directive. An unauthenticated attacker along with conditions beyond their control can exploit this vulnerability by sending crafted HTTP requests. This may cause a heap buffer overflow 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. Impact: 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. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.