Skip to content
VulniPulse
Highest advisory severityCritical 2 vendors · 2 advisories

CVE-2026-42055

CVE-2026-42055: 2 tracked advisory records across F5, Red Hat. Compare vendor sources and published fix guidance.

Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.

Vendor advisory comparison

F5

1 advisory
  • Advisory severityCritical9.2

    Critical [CVE-2026-42055] NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_proxy_v2_module and ngx_http_grpc_module modules

    CVE-2026-42055Source published Source updated

    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…

    Affected products in this advisory
    • NGINX Open Source
    • NGINX Plus
    Source-reported affected versions
    • NGINX Open Source 1.13.10 before 1.31.2
    • NGINX Open Source 1.30.2 before 1.30.3
    • NGINX Plus 37.0 before 37.0.2.1
    • NGINX Plus R36 before R36 P6
    Source-reported fixed versions
    • 1.31.2
    • 1.30.3
    • 37.0.2.1
    • R36 P6
    Mitigation guidance
    No mitigation guidance extracted; consult the source.

Red Hat

1 advisory
  • Advisory severityHigh8.1

    High [CVE-2026-42055] Arbitrary code execution or Denial of Service via heap-based buffer overflow with crafted HTTP/2 headers

    CVE-2026-42055Source published Source updated

    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…

    Affected products in this advisory
    • Red Hat Enterprise Linux 10
    • Red Hat Enterprise Linux 8
    • Red Hat Enterprise Linux 9
    • Red Hat Discovery 2

    4 more entries in the full advisory.

    Source-reported affected versions
    Affected-version details not available in this record.
    Source-reported fixed versions
    • 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

    17 more entries in the full advisory.

    Mitigation guidance
    • 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.

Android app · Google Play

Turn CVE research into alerts on your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery