Quick answers
- Is CVE-2026-92545 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92545 being exploited in the wild.
- How severe is CVE-2026-92545?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Kong Gateway Enterprise; Kong AI Gateway.
- Is there a fix for CVE-2026-92545?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-92545 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-92545?
- Check whether you run Kong AI Gateway or Kong Gateway Enterprise. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The proxy-cache and proxy-cache-advanced plugins in Kong Gateway Enterprise and Kong AI Gateway omit the request hostname from the cache key calculation, causing cache collisions across different hostnames. An attacker can exploit this by making requests to different hostnames and receiving cached responses intended for other hostnames, leading to information disclosure. The vulnerability affects caching logic where hostname-specific responses should be isolated.
Affected products
- Kong Gateway Enterprise
- Kong AI Gateway
Timeline
- 2026-11-10: disclosed