# CVE-2026-92442: Kong Gateway Enterprise graphql-proxy-cache-advanced cache key bypass

Source: https://junglewise.ai/threats/cve-2026-92442-the-graphql-proxy-cache-advanced-plugin-in-kong-gateway  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-92442 · Severity: info · Published 2026-11-10

Kong Gateway Enterprise is an API gateway that manages and secures API traffic. The graphql-proxy-cache-advanced plugin fails to include the caller's identity in its response cache key, allowing cached responses meant for one user to be served to another user. This could expose sensitive data or application logic that should have been restricted.

Technologies: [Kong Gateway Enterprise](https://junglewise.ai/threats/technologies/gateway-enterprise). Vendors: [Kong](https://junglewise.ai/threats/vendors/kong).

## Quick answers

**Is CVE-2026-92442 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-92442 being exploited in the wild.

**How severe is CVE-2026-92442?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** Kong Gateway Enterprise.

**Is there a fix for CVE-2026-92442?** 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-92442 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-92442?** Check whether you run 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 graphql-proxy-cache-advanced plugin in Kong Gateway Enterprise omits caller identity from the cache key generation, resulting in response cache collisions across different authenticated users. An attacker can request a GraphQL query, have it cached, and then cause another user's request for the same query to be served the first attacker's cached response, gaining access to data they should not see. The vulnerability requires the plugin to be enabled and GraphQL queries to be cached.

## Affected products

- Kong Gateway Enterprise

## Timeline

- 2026-11-10: disclosed

## References

- [https://developer.konghq.com/ai-gateway/changelog/](https://developer.konghq.com/ai-gateway/changelog/)
- [https://developer.konghq.com/gateway/changelog/](https://developer.konghq.com/gateway/changelog/)

## Related threats

- [Kong Gateway Enterprise ai-azure-content-safety plugin bypass](https://junglewise.ai/threats/cve-2026-96437-the-ai-azure-content-safety-plugin-in-kong-gateway-enterprise)
- [Kong Gateway Enterprise cache key omission vulnerability](https://junglewise.ai/threats/cve-2026-92545-the-proxy-cache-and-proxy-cache-advanced-plugins-in-kong-gateway)
- [Kong Gateway Enterprise cache poisoning via Authorization header](https://junglewise.ai/threats/cve-2026-92443-the-caching-plugins-in-kong-gateway-enterprise-and-kong-ai)
- [Kong Gateway Enterprise and Kong AI Gateway HTTP header injection via X-Forwarded-Prefix](https://junglewise.ai/threats/cve-2026-92441-kong-gateway-enterprise-and-kong-ai-gateway-include-decoded-cr-lf)
- [Kong Gateway Enterprise SAML plugin audience restriction bypass](https://junglewise.ai/threats/cve-2026-92439-the-saml-plugin-in-kong-gateway-enterprise-does-not-enforce)