Security Advisory: CVE-2026-92545

Severity
High
Published
2026-11-10
Kong Gateway Enterprise
Fixed versions
  • 3.10.0.20
  • 3.13.0.12
  • 3.14.0.17
  • 3.15.0.7
  • 3.16.0.2
Affected versions
  • 3.10.0.0 to < 3.10.0.20
  • 3.13.0.0 to < 3.13.0.12
  • 3.14.0.0 to < 3.14.0.17
  • 3.15.0.0 to < 3.15.0.7
  • 3.16.0.0 to < 3.16.0.2
Kong AI Gateway
Fixed versions
  • 2.2.1
  • 2.3.1
Affected versions
  • 2.2.0
  • 2.3.0

CVE

Description

Severity

Affects Kong

CVE-2026-92545 proxy-cache omits the request authority (Host header) from the cache key High (CVSS 4.0: 8.7) Yes

A high-severity vulnerability in the proxy-cache plugin affects Kong Gateway and Kong AI Gateway.

CVE-2026-92545

The Kong Gateway proxy-cache plugin doesn’t include the request’s hostname (the Host header) in its cache key. A Route or Service reachable under more than one hostname therefore shares a single cache entry across all of them.

As a result, a response generated for one hostname or tenant may be served to requests for another. Where the upstream authenticates per tenant, an unauthenticated request may receive another tenant’s cached, authenticated response without the request reaching the upstream. This can also occur under ordinary multi-tenant traffic without any attacker involvement. The plugin also doesn’t honor the Vary response header, so an upstream that sets Vary: Host can’t prevent this.

  • Severity: High
  • CVSS v4.0 score: 8.7
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • Exploitation: No evidence of exploitation in the wild at this time. Reported through Kong’s HackerOne bug bounty program with a working proof-of-concept; not publicly disclosed.

Am I affected?

You should consider a Kong Gateway deployment potentially affected if all of the following are true:

  • proxy-cache or proxy-cache-advanced is enabled on a Route or Service.
  • The Route or Service is reachable under more than one hostname, or the upstream response varies by hostname (including via X-Forwarded-Host).
  • vary_headers doesn’t include host or an equivalent tenant discriminator.
  • preserve_host is enabled, or the upstream otherwise observes the original hostname.

Customers using the Kong Ingress Controller should note that preserve_host is enabled by default for Ingress-derived Routes. Both the memory and redis cache strategies are affected.

Mitigation

Add host, or an equivalent trusted tenant identifier, to vary_headers on affected proxy-cache and proxy-cache-advanced instances.

Patches

The vulnerability is addressed by applying the patch appropriate for your version:

Impacted supported versions of Kong Gateway Enterprise

Patch

3.10.0.0 - < 3.10.0.20 3.10.0.20
3.13.0.0 - < 3.13.0.12 3.13.0.12
3.14.0.0 - < 3.14.0.17 3.14.0.17
3.15.0.0 - < 3.15.0.7 3.15.0.7
3.16.0.0 - < 3.16.0.2 3.16.0.2

Impacted supported versions of Kong AI Gateway

Patch

2.2.0 2.2.1
2.3.0 2.3.1

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!