← 목록으로 돌아가기

보안 뉴스 · 취약점

2026-022: Critical vulnerabilities in Nginx

출처
CERT-EU
원문 게시일
마지막 본문 수집
2026. 11. 19. 05:00 KST

출처: CERT-EU · © Cybersecurity Service for the Union institutions, bodies, offices and agencies (CERT-EU). · CC BY 4.0
문서 서식과 링크를 FineTS 화면에 맞게 정리했습니다. 이미지·첨부파일은 공식 원문에서 확인하세요.

공식 원문에서 읽기 ↗
기사 원문에 등장한 CVE별 취약점, 설명, 조치사항
취약점설명조치사항
CVE-2026-123007

This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or potentially execute code remotely. 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.

None

CVE-2026-123633

When NGINX Plus or NGINX Open Source is configured to use HTTP/2 for client connections and proxy client requests to a backend, a specially crafted request can result in use-after-free in the worker process, if this process is running low on worker_connections. 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 may allow 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.

None

CVE-2026-121810

Description: This issue affects NGINX Plus and NGINX Open Source configurations that use HTTP/3. A remote, unauthenticated attacker can cause a use-after-free condition in the NGINX worker process, leading to a restart. Exploitation also depends on conditions beyond the attacker’s control. 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.

None

CVE-2026-123634

This issue occurs when NGINX Plus or NGINX Open Source is configured as a proxy, the proxied server name includes variables, and a Server Side Includes (SSI) or mirror directive sends a subrequest to a location that resolves the same server name. Under these conditions, a specially crafted HTTP request may cause a use-after-free condition in a worker process. An attacker may also be able to execute code if Address Space Layout Randomization (ASLR) is disabled or the attacker can bypass ASLR. Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or perform remote code execution (RCE) Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Avoid using SSI or mirror directives and avoid configuring a proxied server name with variables

CVE-2026-113425

When NGINX Plus or NGINX Open Source is configured as a mail proxy, undisclosed traffic can cause a use-after-free in an nginx worker process. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: A remote unauthenticated attacker may crash an nginx worker process or corrupt its memory, disrupting service. Remote code execution is a potential impact. 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.

Restrict listeners to trusted networks.

한국어 버튼을 눌러 번역을 요청할 수 있습니다.

On 18 November 2026, F5 published an advisory addressing five vulnerabilities in NGINX that allow an unauthenticated remote attacker to execute code with the privileges of the NGINX worker process. While researchers managed to successfully demonstrate the use of CVE-2026-123007, no exploitation in t

History:

  • 18/11/2026 --- v1.0 -- Initial publication

Summary

On 18 November 2026, F5 published an advisory addressing five vulnerabilities in NGINX that allow an unauthenticated remote attacker to execute code with the privileges of the NGINX worker process [1, 2].

While researchers managed to successfully demonstrate the use of CVE-2026-123007 [1], no exploitation in the wild has been reported yet.

It is recommended to swiftly update NGINX as soon as possible, prioritising internet facing appliances.

Technical Details

The vulnerability CVE-2026-123007, with a CVSS score of 8.1, is an integer overflow in HTTP/2 flow control which causes an out-of-bounds write on the heap. The only precondition is HTTP/2 enabled on a listening port.

The vulnerability CVE-2026-123633, with a CVSS score of 8.1, is a use-after-free flaw occurring when connection draining closes an active HTTP/2 connection while NGINX connects to an upstream server. HTTP/2 should be enabled and requests should be forwarded to an upstream server.

The vulnerability CVE-2026-121810, with a CVSS score of 8.1, is a use-after-free flaw occurring when a QUIC connection is drained during stream creation and upstream connection. HTTP/3 should be enabled and requests should be forwarded to an upstream server.

The vulnerability CVE-2026-123634, with a CVSS score of 8.1, is a use-after-free flaw occurring in the processing of the DNS resolver waiting list. a resolver must be set, a proxy_pass destination built from request data, and mirror with mirror_request_body off should be configured.

The vulnerability CVE-2026-113425, with a CVSS score of 8.1, is a use-after-free occurring when the client closes the connection during the auth_http authentication lookup. A mail proxy must be configured with proxy on and auth_http.

All five vulnerabilities can lead to unauthenticated code execution with the privileges of the NGINX worker process [1].

Affected Products

The following products and versions are affected by one or more of the above vulnerabilities:

  • NGINX Open Source (mainline) from version 1.9.5 to 1.31.8 (range depends on the vulnerability, see Technical Details) [1]. Refer to the vendor advisory for the information on fixed versions [2].
  • NGINX Open Source (stable) versions 1.30.x, including the current stable version 1.30.6 [1, 3]. Refer to the vendor advisory for the information on fixed versions [2].
  • NGINX Plus from version 37.0.0 to 37.0.7.1, and 37.1.0 to 37.2.0.1. The versions R34, R35 and R36 are also affected [2]. Refer to the vendor advisory for the information on fixed versions [2].

Recommendations

CERT-EU recommends updating vulnerable instance as soon as possible, prioritising internet-facing devices.

Compromise assessment

It is possible to monitor for crashes of the Nginx worker (worker process … exited on signal in the error log). However, this is not a high-fidelity indicator of successful remote code execution but rather an indication of exploitation attempts. Further checks in the process creation logs are necessary.

Mitigation

When updating is not immediately possible, disabling HTTP/2 on exposed listeners (by removing the http2 from the listen directives, or set http2 off;) mitigates the vulnerabilities CVE-2026-123007 and CVE-2026-123633 [1].

References

[1] https://xint.io/blog/nginx2root-remote-code-execution

[2] https://my.f5.com/manage/s/article/K000164058

[3] https://nginx.org/en/security_advisories.html

공식 원문에서 읽기 ↗

← 목록으로 돌아가기