#Server Security

CVE-2026-97205: Critical Vulnerability in NGINX

A critical vulnerability in NGINX may allow remote code execution.

CVE-2026-97205: Critical Vulnerability in NGINX

Introduction

The CVE-2026-97205 vulnerability affects both NGINX Plus and NGINX Open Source, specifically within the ngx_http_core_module. This flaw can have severe consequences, including the potential for remote code execution.

What happened?

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) condition in the NGINX worker process. This can lead to memory corruption or even a worker process crash.

How does the vulnerability work?

The vulnerability arises from how NGINX handles memory when AIO is enabled. Improper memory usage may allow an attacker, particularly on systems where Address Space Layout Randomization (ASLR) is disabled, to execute malicious code. This issue is classified as a Use-After-Free flaw, which is a common cause of memory corruption.

What is the real impact?

The impact of this vulnerability is significant, as it may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system, corrupt its memory, or in more severe cases, execute malicious code. It is important to note that there is no control plane exposure; this is a data plane issue only.

Which versions are affected?

  • dos ≥ 4.5.0 ≤ 4.7.0
  • dos ≥ 4.8.0 ≤ 4.10.0
  • nginx gateway fabric ≥ 2.1.0 ≤ 2.7.2
  • nginx ingress controller ≥ 5.6.0 < 5.7.0
  • nginx instance manager ≥ 2.18.0 < 2.24.0
  • nginx open source ≥ 0.8.11 < 1.30.6
  • nginx open source ≥ 1.31.0 < 1.31.7
  • nginx plus ≥ 37.0.0 ≤ 37.0.4
  • nginx plus ≥ 37.1.0 < 37.1.0.1
  • nginx plus r33
  • nginx plus r34
  • nginx plus r35

How to fix

  1. Check your NGINX version and identify if it is among the affected versions.
  2. Refer to the vendor's advisory for information on fixed versions.
  3. Update NGINX to a version that is not affected by the vulnerability.
  4. Review AIO settings and consider disabling them if they are not necessary.
  5. Monitor system logs for suspicious activity.

Mitigation while you update

While it is not possible to update immediately, consider disabling AIO functionality in NGINX settings. Additionally, implement firewall rules to limit access to the server and protect it against potential attacks.

Conclusion

The CVE-2026-97205 vulnerability poses a significant risk to NGINX systems. It is crucial for system administrators to take immediate action to address or mitigate this flaw, ensuring the security and stability of their services.

// Fontes

  1. NVD — CVE-2026-97205 nvd.nist.gov ↗
  2. CVE.org — CVE-2026-97205 cve.org ↗
  3. my.f5.com (vendor advisory) my.f5.com ↗

// ++ — related