Security Advisory: CVE-2023-44487 HTTP/2 denial of service

Severity
Critical
Published
2026-10-13
Kong Gateway Enterprise
Fixed versions
  • 2.8.4.4
  • 3.1.1.6
  • 3.2.2.5
  • 3.3.1.1
  • 3.4.1.1
Affected versions
  • 2.8.x.y
  • 3.1.x.y
  • 3.2.x.y
  • 3.3.x.y
  • 3.4.x.y
Kong Mesh
Fixed versions
  • 2.0.8
  • 2.1.7
  • 2.2.5
  • 2.3.3
  • 2.4.3
Affected versions
  • 2.0.x
  • 2.1.x
  • 2.2.x
  • 2.3.x
  • 2.4.x

CVE

Description

Severity

CVE-2023-44487 HTTP/2 denial of service through rapid stream request cancellation Critical

A significant security vulnerability has been discovered in the HTTP/2 protocol that allows the possibility of denial-of-service attacks against a wide range of technologies implementing the protocol, including Kong Gateway and Kong Mesh. Kong strongly recommends that impacted customers take the recommended steps to address this vulnerability as soon as possible.

CVE-2023-44487

The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly. An attacker can overwhelm an impacted gateway or a data plane by sending a very large number of HTTP/2 stream requests and resetting them rapidly, causing too much resource consumption on the server.

CVE-2023-44487 is the public declaration of the vulnerability.

Impacted products

  • Kong Gateway Enterprise, all versions
  • Kong Konnect using Kong Gateway Enterprise, all versions
  • Kong Mesh, all versions

Patches

Kong has prepared patches for most of the versions under active support and is actively publishing these. The vulnerability is addressed by applying the following patches.

Impacted Kong Gateway Enterprise version

Patch

2.8.x.y 2.8.4.4
3.1.x.y 3.1.1.6
3.2.x.y 3.2.2.5
3.3.x.y 3.3.1.1
3.4.x.y 3.4.1.1

Impacted Kong Mesh version

Patch

2.0.x 2.0.8
2.1.x 2.1.7
2.2.x 2.2.5
2.3.x 2.3.3
2.4.x 2.4.3

Patches for all Kong distributions are or will be available through standard Kong distribution channels.

Mitigation

Upgrading Kong to a patched version that contains the appropriate fix for the vulnerability is the recommended first step. When rolling out an update isn’t possible, you can take the following steps as temporary measures to mitigate the issue.

Kong Gateway: Disable HTTP/2 support in Kong

Several listeners can be configured to use HTTP/2.

These listeners default to HTTP/2:

  • proxy_port
  • admin_port

These listeners are configurable to use HTTP/2:

  • debug_listen
  • status_listen
  • admin_gui_listen
  • portal_gui_listen
  • portal_api_listen

To disable this support, remove the http2 suffix from the specified port in your kong.conf file, environment variables, values, or similar configuration.

For example, before:

proxy_listen = 0.0.0.0:8000 , 0.0.0.0:8443 http2 ssl reuseport backlog=16384
admin_listen = 127.0.0.1:8001, 127.0.0.1:8444 http2 ssl reuseport backlog=16384

After:

proxy_listen = 0.0.0.0:8000, 0.0.0.0:8443 ssl reuseport backlog=16384
admin_listen = 127.0.0.1:8001, 127.0.0.1:8444 ssl reuseport backlog=16384

By default, the Admin API only accepts requests over the loopback interface. The Admin API listener is included here for completeness, for instances where this was changed.

If you have a load balancer in front of Kong nodes and the traffic between the load balancer and Kong nodes is unencrypted, then you aren’t affected unless you have explicitly enabled HTTP/2 by adding the http2 suffix to your listener. Plaintext HTTP/2 isn’t enabled by default.

Additionally, requests arriving through a CDN (Akamai, Cloudflare, CloudFront, and so on) are typically protected against this attack through their own mitigation steps.

Contact

If you have questions or need help, open a case with Kong Support or email support@konghq.com.

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!