RHSA-2026:100755CriticalCVSS 8.2

Red Hat Security Advisory: nginx:1.24 security update

Published
November 20, 2026
Last Modified
November 21, 2026

🔗 CVE IDs covered (12)

📋 Description

CVE-2026-9256 — nginx: ngx_http_rewrite_module: code execution and denial of service CVE-2026-15176 — nginx: nginx: heap-based buffer overflow in ngx_http_core_module via alias with rewrite referencing $request_filename CVE-2026-42055 — nginx: NGINX: Arbitrary code execution or Denial of Service via heap-based buffer overflow with crafted HTTP/2 headers CVE-2026-42533 — nginx: NGINX: Arbitrary code execution via crafted HTTP requests CVE-2026-56434 — nginx: NGINX: Heap buffer over-read allows memory modification or denial of service CVE-2026-60005 — nginx: NGINX: Memory disclosure and denial of service in ngx_http_slice_module CVE-2026-97205 — nginx: NGINX ngx_http_core_module vulnerability CVE-2026-113425 — nginx: NGINX use-after-free in worker process in the mail proxy server CVE-2026-118899 — nginx: nginx: Denial of Service via crafted TLS connection CVE-2026-123007 — nginx: NGINX flow control window overflow in HTTP/2 CVE-2026-123633 — nginx: NGINX use-after-free in worker process when using HTTP/2 CVE-2026-123634 — nginx: NGINX use-after-free condition in the resolver

🎯 Affected products68

  • Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.aarch64 (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.ppc64le (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.s390x (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.src (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.x86_64 (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-all-modules-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.noarch (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-core-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.aarch64 (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-core-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.ppc64le (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-core-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.s390x (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-core-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.x86_64 (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-core-debuginfo-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.aarch64 (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-core-debuginfo-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.ppc64le (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-core-debuginfo-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.s390x (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-core-debuginfo-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.x86_64 (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-debuginfo-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.aarch64 (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-debuginfo-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.ppc64le (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-debuginfo-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.s390x (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-debuginfo-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.x86_64 (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-debugsource-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.aarch64 (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-debugsource-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.ppc64le (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-debugsource-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.s390x (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-debugsource-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.x86_64 (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-filesystem-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.noarch (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-mod-devel-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.aarch64 (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-mod-devel-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.ppc64le (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-mod-devel-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.s390x (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-mod-devel-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.x86_64 (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-mod-http-image-filter-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.aarch64 (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • nginx-mod-http-image-filter-1:1.24.0-1.module+el9.4.0+25370+afae48b9.6.ppc64le (nginx:1.24) as a component of Red Hat Enterprise Linux AppStream E4S (v.9.4)
  • +38 more not shown

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: To mitigate this vulnerability, use named captures instead of unnamed captures in rewrite definitions. For example, the following rewrite directive uses unnamed PCRE capture groups, $1 and $2: ~~~ rewrite ^/users/([0-9]+)/profile/(.*)$ /profile.php?id=$1&tab=$2 last; ~~~ To mitigate this vulnerability for this example, replace $1 and $2 with the appropriate named captures, $user_id and $section: ~~~ rewrite ^/users/(?<user_id>[0-9]+)/profile/(?<section>.*)$ /profile.php?id=$user_id&tab=$section last; ~~~ Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: To mitigate this vulnerability, ensure that the `ignore_invalid_headers` directive is set to `on` in your NGINX configuration, or reduce the size specified by the `large_client_header_buffers` directive to 2 megabytes or less. These changes require an NGINX service reload or restart to take effect. Reloading the NGINX service is generally safe, but a restart will briefly interrupt service. Workaround: To mitigate this vulnerability, do not use unnamed captures. Use named captures instead and only use them in the same block with the regex match. Red Hat recommends updating nginx to the latest version when a fix is available. Workaround: To prevent exploitation, avoid configuring NGINX with `ngx_http_ssi_module` when `proxy_pass` and `proxy_buffering off` are simultaneously active. If Server-Side Includes (SSI) are not essential, disable the `ngx_http_ssi_module` by removing or commenting out the `ssi on;` directive. Alternatively, ensure `proxy_buffering` is explicitly enabled (`proxy_buffering on;`) when `proxy_pass` is used with SSI. A reload or restart of the NGINX service is necessary for configuration changes to apply, which may cause a brief service interruption. Workaround: To mitigate this issue, disable the ngx_http_slice_module entirely if it is not required. If the module must be used, avoid unnamed regex captures with the slice directive and explicitly disable proxy_cache_background_update. Reload or restart the NGINX service to apply these changes. Please note this may cause a brief service interruption. Workaround: To mitigate this vulnerability, based on your environment requirements, you can either disable asynchronous file I/O (AIO) or Server Side Includes (SSI). Workaround: See the security bulletin for a detailed mitigation procedure. Workaround: Disable TLSv1.3 protocol support in the NGINX configuration to restrict connections to TLSv1.2, or restrict access to trusted networks using firewall rules. To disable TLSv1.3: 1. Edit the NGINX configuration file (such as `/etc/nginx/nginx.conf` or configuration snippets under `/etc/nginx/conf.d/`). 2. Locate the `ssl_protocols` directive within the `http` or `server` blocks and set it to allow only TLSv1.2: ``` ssl_protocols TLSv1.2; ``` 3. Verify the configuration syntax: ```sh nginx -t ``` 4. Reload the NGINX service to apply configuration changes: ```sh systemctl reload nginx ``` Alternatively, if the service only needs to be reached by specific clients, use firewalld to limit network exposure: ```sh firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_IP_RANGE> firewall-cmd --reload ``` Caveats: Disabling TLSv1.3 prevents clients that strictly require TLSv1.3 from connecting and removes the performance and cryptographic improvements introduced in that version. Warning: Reloading the NGINX service is required for configuration changes to take effect and may cause momentary disruption to existing connections.

🔗 References (15)