High [CVE-2026-42055] Arbitrary code execution or Denial of Service via heap-based buffer overflow with crafted HTTP/2 headers
This high-severity Red Hat Linux advisory covers CVE-2026-42055 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_proxy_v2_module and ngx_http_grpc_module modules.
This vulnerability exists when the proxy_http_version to 2 or grpc_pass directives are used to proxy HTTP/2 traffic, the ignore_invalid_headers directive is set to off, and the large_client_header_buffers directive size is larger than 2 megabytes.
A remote, unauthenticated attacker, along with conditions beyond their control, could send large headers while creating an upstream request. This may cause a heap-based 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. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
A flaw was found in NGINX. When NGINX is configured to proxy HTTP/2 traffic using the ngx_http_proxy_v2_module or ngx_http_grpc_module with specific settings, a remote, unauthenticated attacker can send specially crafted large headers.
Under certain conditions, such as when Address Space Layout Randomization (ASLR) is disabled or bypassed, this vulnerability could also allow for arbitrary code execution. Red Hat severity: Important — CVSS 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).
Weakness: CWE-131.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 16 days ago·verify at source
- nginx-2:1.26.3-6.el10_2.5
- nginx:1.24-8100020260707171317.489197e6
- nginx-2:1.20.1-28.el9_8.4
- nginx:1.24-9080020260707164406.9
- nginx:1.26-9080020260707110000.9
- discovery/discovery-ui-rhel9:1784821750
- nginx-main-1.30.3-2.hum1
- rhui5/cds-kubernetes-rhel9:1784794818
- rhui5/cds-rhel9:1784794778
- rhui5/rhua-rhel9:1784795076
- RHSA-2026:36364
- RHSA-2026:38847
- RHSA-2026:36331
- RHSA-2026:36618
- RHSA-2026:36639
- RHSA-2026:46836
- RHSA-2026:27197
- RHSA-2026:44481
Official advisory · high-confidence parse· fetched 16 days ago·verify at source
Mitigation checklist
- 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.
Official advisory · high-confidence parse· fetched 16 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.