CVE-2026-42055: NGINX HTTP/2 and gRPC Upstream Heap Buffer Overflow
- Vendors
- Red HatF5
CVE-2026-42055 is a heap-based buffer overflow in the ngx_http_proxy_v2_module and ngx_http_grpc_module modules of NGINX Plus and NGINX Open Source. The vulnerability occurs during upstream request creation when HTTP/2 proxying is configured using proxy_http_version 2 or grpc_pass, ignore_invalid_headers is off, and the large_client_header_buffers buffer size exceeds 2 megabytes. A remote, unauthenticated attacker sending crafted large headers, subject to additional conditions outside the attacker's control, can corrupt heap memory in an NGINX worker process. Exploitation can cause a worker restart or permit arbitrary code execution if Address Space Layout Randomization (ASLR) is disabled or bypassed.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Exploitation can crash and restart an NGINX worker process, disrupting request processing and potentially causing denial of service. If ASLR is disabled or successfully bypassed, the heap corruption can enable arbitrary code execution in the worker-process security context, potentially compromising the confidentiality, integrity, and availability of resources accessible to that process.
Mitigation
If you can’t patch tonight, do this now.
Break the required configuration combination: enable invalid-header filtering by setting ignore_invalid_headers to on, reduce the large_client_header_buffers buffer size to 2 megabytes or less, or disable the affected HTTP/2 upstream proxying configuration where operationally feasible. Keep ASLR enabled as defense in depth, but do not treat it as a complete mitigation because worker crashes remain possible and ASLR bypass may permit code execution.
Remediation
Patch, then assume compromise.
Install the vendor-supported security update for the applicable NGINX product or distribution. The upstream mainline fix was first included in nginx 1.31.2; distribution-maintained branches may contain backported fixes under older upstream version numbers. Corrected packages include Debian trixie nginx 1.26.3-3+deb13u7 and RHEL nginx releases 1.20.1-22.el9_6.7, 1.20.1-16.el9_4.7, and 1.20.1-14.el9_2.7 for their respective support streams. Applicable Tanzu fixes include NGINX Buildpack 1.2.91 and Staticfile Buildpack 1.6.91. Versions beyond End of Technical Support were not evaluated; migrate such installations to a supported, patched release.
Exploits
No validated public exploits yet. Hidden: 2 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-42055 exploited in the wild?
- As of Nov 19, 2026, Mallory has no reports of CVE-2026-42055 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-42055?
- As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-42055.
- Is there a patch for CVE-2026-42055?
- Install the vendor-supported security update for the applicable NGINX product or distribution. The upstream mainline fix was first included in nginx 1.31.2; distribution-maintained branches may contain backported fixes under older upstream version numbers.
- What products are affected by CVE-2026-42055?
- F5 Nginx, F5 Nginx Plus, Red Hat Discovery, F5 Dos, Red Hat Hardened Images, and 8 more.
- How severe is CVE-2026-42055?
- CVE-2026-42055 has a CVSS v4 score of 9.2 (Critical) and an EPSS score of 6.5% (94th percentile) as of Nov 19, 2026.
Recent activity
83 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.