---
id: "CVE-2026-92545"
page: "https://infrastack.ai/live/CVE-2026-92545"
kind: "vulnerability"
aliases: ["CVE-2026-92545"]
title: "Kong Gateway: cache serves one hostname's response to another hostname"
severity: "high"
cvss: 8.7
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: [{"name": "Kong Gateway Enterprise", "fixed": ["3.16.0.2"], "affected": "below 3.16.0.2 (3.16 line; older branch ranges unconfirmed)", "ecosystem": "vendor"}]
ecosystems: []
tags: ["api-gateway", "enterprise", "infrastructure", "kong", "proxy-cache", "self-hosted"]
not_affected_if: ["caching-plugins-disabled", "proxy-cache-not-enabled", "single-hostname"]
published_at: "2026-11-10T22:21:15+00:00"
first_seen_at: "2026-11-10T22:27:31+00:00"
updated_at: "2026-11-10T22:37:17+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-92545", "first_seen_at": "2026-11-10T22:27:31+00:00"}, {"source": "analyst", "url": "https://developer.konghq.com/gateway/changelog/", "first_seen_at": "2026-11-10T22:37:17+00:00", "cites": ["https://developer.konghq.com/gateway/changelog/", "https://vuln.mlab.sh/cna/Kong"]}]
exploit_sources: []
---

# Kong Gateway: cache serves one hostname's response to another hostname

Link for people: https://infrastack.ai/live/CVE-2026-92545 (this .md is for agents)

The proxy-cache and proxy-cache-advanced plugins in Kong Gateway Enterprise and Kong AI Gateway leave the request hostname out of the cache key. A response cached for one hostname can therefore be served to requests meant for another hostname, exposing that content to the wrong client.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:Kong Gateway Enterprise affected below 3.16.0.2 (3.16 line; older branch ranges unconfirmed) fixed 3.16.0.2

## How to check

Run Kong Gateway Enterprise or Kong AI Gateway with the proxy-cache or proxy-cache-advanced plugin enabled (also graphql-proxy-cache-advanced)? Check the plugin list in the Admin API (GET /plugins) and your version (kong version). Exposed if the plugin is enabled, the version is below the fix, and one cache serves more than one hostname (several Hosts on one route or service). A single hostname is not affected by this.

## Fix

Kong Gateway Enterprise 3.16.0.2 (released 2026-11-10) adds the hostname to the proxy-cache, proxy-cache-advanced and graphql-proxy-cache-advanced cache key. Fixed versions for 3.14, 3.13 and other branches are not stated in the changelog I could read; check Kong's advisory at konghq.com/compliance/psa.

## Timeline

- 2026-11-10T22:27:31+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-92545
- 2026-11-10T22:37:17+00:00 analyst https://developer.konghq.com/gateway/changelog/ — Kong changelog 3.16.0.2 (2026-11-10) lists CVE-2026-92545 fixed in proxy-cache, proxy-cache-advanced, graphql-proxy-cache-advanced via hostname in cache key. CNA CVSS 8.7. NVD page returned nothing and Kong's PSA article was not readable; backports to 3.14/3.13 and AI Gateway versions unconfirmed. No exploitation or PoC seen; did not search social.

## Documents

- [fix] Kong Gateway changelog (3.16.0.2) https://developer.konghq.com/gateway/changelog/
- [mentions] Kong CNA CVE list (CVE-2026-92545, CVSS 8.7) https://vuln.mlab.sh/cna/Kong

## From the sources

The proxy-cache and proxy-cache-advanced plugins in Kong Gateway Enterprise and Kong AI Gateway omit the request hostname from the cache key which may allow a response cached for a hostname to be served for another.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_