Skip to main content
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 critical memory corruption vulnerability affecting NGINX Plus and NGINX Open Source in the ngx_http_proxy_v2_module and ngx_http_grpc_module modules. The flaw is reachable when NGINX is configured to proxy HTTP/2 traffic using proxy_http_version 2 or grpc_pass, with ignore_invalid_headers set to off and large_client_header_buffers configured larger than 2 megabytes. Under these conditions, a remote, unauthenticated attacker can send large headers while an upstream request is being created, triggering a heap-based buffer overflow in the NGINX worker process. The issue can cause the worker process to restart and, on systems where ASLR is disabled or can be bypassed, may be leveraged for arbitrary 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 or restart the NGINX worker process, resulting in denial of service. Because the flaw is a heap-based buffer overflow, it also creates a path to arbitrary code execution in the worker context on systems with ASLR disabled or where the attacker can otherwise bypass ASLR.

Mitigation

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

If immediate patching is not possible, avoid the vulnerable configuration combination. Remove ignore_invalid_headers off so invalid-header filtering remains enabled, and reduce large_client_header_buffers to 2 megabytes or less. Also avoid using proxy_http_version 2 or grpc_pass for HTTP/2 proxying in configurations that would otherwise meet the vulnerable conditions until fixed versions are deployed.

Remediation

Patch, then assume compromise.

Upgrade NGINX Plus and NGINX Open Source to a vendor-fixed release. The provided content indicates fixes were released in nginx 1.31.2 and stable branch 1.30.3, and F5 also issued out-of-band security updates for affected NGINX products. After patching, verify that HTTP/2 proxying and gRPC configurations are using corrected builds and review header-handling settings in affected deployments.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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 Plusapplication
NginxNginxapplication

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

ACTIVITY FEED

Recent activity

10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

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 activity4

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