When NGINX Open Source is configured to proxy HTTP/2 traffic by setting proxy_http_version to 2, and also uses proxy_set_body, an attacker may be able to inject frame…

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

1. May 13, 2026 · NIST NVD

   Detected

   When NGINX Open Source is configured to proxy HTTP/2 traffic by setting proxy_http_version to 2, and also uses proxy_set_body, an attacker may be able to inject frame headers and payload bytes to the upstream peer. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

2. Jun 18, 2026 · NIST NVD

   Updated

   When NGINX Open Source is configured to proxy HTTP/2 traffic by setting proxy_http_version to 2, and also uses proxy_set_body, an attacker may be able to inject frame headers and payload bytes to the upstream peer. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Affected

• cpe f5/nginx gateway fabricversion unspecified
• cpe f5/nginx ingress controllerversion unspecified
• cpe f5/nginx instance managerversion unspecified
• cpe f5/nginx open sourceversion unspecified

Sources

• CVE.orgVulnerability recordCVE-2026-42926

  Official CVE identifier

  cve.org
• NIST NVDVulnerability recordCVE-2026-42926

  When NGINX Open Source is configured to proxy HTTP/2 traffic by setting proxy_http_version to 2, and also uses proxy_set_body, an attacker may be able to inject frame headers and payload bytes to the upstream peer. Note: Software versions which have reached End of Technical Supp

  nvd.nist.gov

References

• Mitigation · my.f5.com