CVE-2026-92545: Kong Gateway Enterprise · Use of Cache Containing Sensitive Information
Affects Kong Gateway EnterpriseSource CVE Database V5
Not known to be exploited · CVSS 8.7 High · fixed in 3.16.0.2 : patch Kong Gateway Enterprise soon.
Data as of 10 Nov 2026, 21:34 UTC
Thin evidence
One scorer or none| CNA (Kong) | CVSS 4.0 | 8.7 |
|---|
- Patch
- Available – fixed in 3.16.0.2, 3.15.0.7, 3.14.0.17 +3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Kong Inc.Kong Gateway Enterprise | Affected
| Fixed in
|
| Kong Inc.Kong Gateway Enterprise | Affected
| Fixed in
|
| Kong Inc.Kong Gateway Enterprise | Affected
| Fixed in
|
| Kong Inc.Kong Gateway Enterprise | Affected
| Fixed in
|
| Kong Inc.Kong Gateway Enterprise | Affected
| Fixed in
|
| Kong Inc.Kong AI Gateway | Affected
| Fixed in
|
AI-suggested
Fixed versions are available: 2.2.1, 3.10.0.20, 3.13.0.12, 3.14.0.17, 3.15.0.7, and 3.16.0.2. Users should upgrade to these versions to remediate the vulnerability. No other mitigation or temporary fixes are indicated in the provided data.
Description
CVE-2026-92545 is a vulnerability in Kong Gateway Enterprise and Kong AI Gateway where the proxy-cache and proxy-cache-advanced plugins do not include the request hostname in the cache key. This omission can cause cached responses intended for one hostname to be served to requests for a different hostname, potentially exposing sensitive information. The issue affects multiple versions prior to fixed releases. The vulnerability has a high severity score of 8.7 and is classified under CWE-524 (Use of Cache Containing Sensitive Information).