A critical-severity NGINX buffer overflow may affect Kong API Gateway Enterprise and Kong AI Gateway Enterprise when HTTP/2 or gRPC upstream proxying is combined with specific non-default settings.
Security Advisory: CVE-2026-42055
- 3.15.0.3
- 3.14.0.12
- 3.13.0.9
- 3.12.0.10
- 3.10.0.17
- 3.4.3.29
- 3.15.0.0 to 3.15.0.2
- 3.14.0.0 to 3.14.0.11
- 3.13.0.0 to 3.13.0.8
- 3.12.0.0 to 3.12.0.9
- 3.10.0.0 to 3.10.0.16
- 3.4.0.0 to 3.4.3.28
|
CVE |
Description |
Severity |
Affects Kong |
|---|---|---|---|
| CVE-2026-42055 | NGINX HTTP/2 and gRPC upstream heap buffer overflow | Critical (CVSS 4.0: 9.2) | Yes |
CVE-2026-42055
Kong API Gateway Enterprise and Kong AI Gateway Enterprise include NGINX/OpenResty and support proxying traffic to gRPC upstream services. They may be affected when HTTP/2 or gRPC upstream proxying is combined with specific non-default request-header configuration settings.
A remote, unauthenticated attacker with network access to an affected HTTP or gRPC listener could send crafted requests containing large headers while Kong is constructing an upstream request. This may trigger a heap-based buffer overflow in an NGINX worker process, causing the worker to restart and potentially resulting in service degradation or a denial-of-service (DoS) condition.
Under limited circumstances where Address Space Layout Randomization (ASLR) is disabled or can be bypassed, successful exploitation may also allow arbitrary code execution.
- Severity: Critical
- CVSS v4.0 score: 9.2
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Am I affected?
You should consider a Kong Gateway deployment affected if all of the following are true:
- The deployment proxies HTTP/2 upstream traffic using
proxy_http_version 2, or proxies traffic to a gRPC upstream usinggrpc_pass. - The NGINX
ignore_invalid_headersdirective is explicitly set tooff. - The size component of the
large_client_header_buffersdirective is configured to a value greater than 2 megabytes, for examplelarge_client_header_buffers 4 4m; - The affected proxy listener is reachable by untrusted clients or exposed to the internet.
The published vulnerability conditions are not met by the default Kong configuration. Kong configures large_client_header_buffers as 4 8k by default, while NGINX enables ignore_invalid_headers by default. Deployments using these default values are not affected, including deployments that use gRPC without the two additional vulnerable configuration settings.
Impacted products
All Kong API Gateway Enterprise versions prior to the patch versions listed in the Patches section.
Patches
The vulnerability is addressed by applying the following patch:
|
Impacted supported versions of Kong API Gateway Enterprise |
Patch |
|---|---|
| 3.15.0.0 - 3.15.0.2 | 3.15.0.3 |
| 3.14.0.0 - 3.14.0.11 | 3.14.0.12 |
| 3.13.0.0 - 3.13.0.8 | 3.13.0.9 |
| 3.12.0.0 - 3.12.0.9 | 3.12.0.10 |
| 3.10.0.0 - 3.10.0.16 | 3.10.0.17 |
| 3.4.0.0 - 3.4.3.28 | 3.4.3.29 |
Contact
If you have questions or need help, open a case with Kong Support or email support@konghq.com.