Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Unrated

Heap-based Buffer Overflow in NGINX ngx_http_proxy_v2_module and ngx_http_grpc_module

IdentifiersCVE-2026-42055CWE-122

CVE-2026-42055 is a heap-based buffer overflow in NGINX Plus and NGINX Open Source affecting the ngx_http_proxy_v2_module and ngx_http_grpc_module. The flaw is reachable when NGINX is configured to proxy HTTP/2 traffic to upstreams using proxy_http_version 2 or grpc_pass, with ignore_invalid_headers set to off and large_client_header_buffers configured larger than 2 MB. Under those non-default conditions, a remote unauthenticated attacker can send oversized or malformed headers during upstream request creation, triggering memory corruption in the NGINX worker process. The immediate result is typically a worker crash and restart; on systems where ASLR is disabled, or where an attacker can otherwise bypass ASLR, the memory corruption may be leveraged for code execution.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can crash the affected NGINX worker process and force a restart, resulting in denial of service or service instability. Because this is heap memory corruption, the impact can extend beyond DoS: on systems with ASLR disabled, or where ASLR can be bypassed, the vulnerability may be exploitable for arbitrary code execution in the context of the NGINX worker process.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, remove the vulnerable configuration combination. Specifically, do not use proxy_http_version 2 or grpc_pass for HTTP/2 upstream proxying together with ignore_invalid_headers off and large_client_header_buffers greater than 2 MB. Restore ignore_invalid_headers to its default behavior and/or reduce large_client_header_buffers to 2 MB or less until fixed releases can be deployed.

Remediation

Patch, then assume compromise.

Upgrade to a fixed vendor release. The provided content indicates fixes are available in NGINX Open Source 1.31.2 and 1.30.3, and in NGINX Plus 37.0.2.1 and R36 P6. Apply the corresponding F5/NGINX security updates for supported downstream products and branches. After patching, verify that affected proxy and header-handling configurations have been reviewed and that no unsupported or end-of-technical-support versions remain deployed.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

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.

VendorProductType
F5Nginxapplication
F5Nginx Open Sourceapplication
F5Nginx Plusapplication
NginxNginxapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity25

Community discussion across Reddit, Mastodon, and other social sources.