A high-severity caller isolation vulnerability in the graphql-proxy-cache-advanced plugin affects Kong Gateway Enterprise and Kong AI Gateway.
Security Advisory: CVE-2026-92442
- 3.10.0.20
- 3.13.0.12
- 3.14.0.17
- 3.15.0.7
- 3.16.0.2
- 3.10.0.0 to < 3.10.0.20
- 3.13.0.0 to < 3.13.0.12
- 3.14.0.0 to < 3.14.0.17
- 3.15.0.0 to < 3.15.0.7
- 3.16.0.0 to < 3.16.0.2
- 2.2.1
- 2.3.1
- 2.2.0
- 2.3.0
|
CVE |
Description |
Severity |
Affects Kong |
|---|---|---|---|
| CVE-2026-92442 |
graphql-proxy-cache-advanced cache key is missing caller isolation
|
High (CVSS 4.0: 8.3) | Yes |
CVE-2026-92442
The Kong Gateway Enterprise graphql-proxy-cache-advanced plugin doesn’t include the caller’s identity in its cache key. Callers using the same Route and GraphQL request may therefore share a cache entry even when the upstream response is specific to a user or tenant. This applies whether authentication is performed by Kong or by the upstream application.
Where Kong performs authentication, one Consumer may receive a response generated for another. Where the upstream performs authentication, a response cached for an authenticated user may be returned to an unauthenticated caller without the request reaching the upstream.
- Severity: High
- CVSS v4.0 score: 8.3
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N
- Exploitation: No evidence of exploitation in the wild at this time. Reported through Kong’s HackerOne bug bounty program with a working proof-of-concept; not publicly disclosed.
Am I affected?
You should consider a Kong Gateway Enterprise deployment potentially affected if all of the following are true:
graphql-proxy-cache-advancedis enabled.- Multiple users, Consumers, or tenants use the same cached Route, and the upstream response can vary by caller.
vary_headersdoesn’t contain a trusted caller-identity value.
Both the memory and redis cache strategies are affected.
Mitigation
Where the upstream application performs authentication, set vary_headers to include authorization. Where Kong performs authentication, vary on a trusted Kong-generated Consumer identifier such as x-consumer-username. If no suitable identity value can be included in the cache key, disable the plugin for caller-specific responses. Don’t rely on upstream Cache-Control: private or no-store as the only mitigation.
Patches
The vulnerability is addressed by applying the patch appropriate for your version:
|
Impacted supported versions of Kong Gateway Enterprise |
Patch |
|---|---|
| 3.10.0.0 - < 3.10.0.20 | 3.10.0.20 |
| 3.13.0.0 - < 3.13.0.12 | 3.13.0.12 |
| 3.14.0.0 - < 3.14.0.17 | 3.14.0.17 |
| 3.15.0.0 - < 3.15.0.7 | 3.15.0.7 |
| 3.16.0.0 - < 3.16.0.2 | 3.16.0.2 |
|
Impacted supported versions of Kong AI Gateway |
Patch |
|---|---|
| 2.2.0 | 2.2.1 |
| 2.3.0 | 2.3.1 |
Contact
If you have questions or need help, open a case with Kong Support or email support@konghq.com.