KONG GATEWAY ENTERPRISE · CVE-2026-92545 · Infrastructure
FIX → 3.16.0.2 ✓ verified
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.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running Kong Gateway Enterprise or Kong AI Gateway with the proxy-cache or proxy-cache-advanced plugin enabled, where one gateway serves several hostnames. Gateways without these plugins, or with caching off, are not exposed by this description. The sources do not list affected versions.
Not affected if caching-plugins-disabled, proxy-cache-not-enabled, single-hostname
Who cares api-gateway, enterprise, kong, proxy-cache, self-hosted
Upgrade to 3.16.0.2
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.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
3.16.0.2