A high-severity vulnerability in the Kong Gateway caching plugins affects Kong Gateway Enterprise and Kong AI Gateway.
Security Advisory: CVE-2026-92443
- 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.2.0
|
CVE |
Description |
Severity |
Affects Kong |
|---|---|---|---|
| CVE-2026-92443 |
Caching plugins may serve a cached response to callers when the request carried an Authorization header
|
High (CVSS 4.0: 8.2) | Yes |
CVE-2026-92443
The Kong Gateway proxy-cache, proxy-cache-advanced, graphql-proxy-cache-advanced, and ai-semantic-cache plugins may cache a response to a request that carried an Authorization or Proxy-Authorization header, and later serve that response to a caller that sends no credentials.
Where the upstream application performs authentication, a response cached for an authenticated user may be returned to a caller that sends no credentials, without the request reaching the upstream. Where a Kong authentication plugin authenticates the request, the Consumer is part of the cache key and responses aren’t shared between Consumers. For ai-semantic-cache, the cached content is the LLM completion, which may include tenant-specific prompts and retrieved context.
- Severity: High
- CVSS v4.0 score: 8.2
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/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 or Kong AI Gateway deployment potentially affected if all of the following are true:
proxy-cache,proxy-cache-advanced,graphql-proxy-cache-advanced, orai-semantic-cacheis enabled on a Route or Service.- Authentication for that Route is performed by the upstream application using the
AuthorizationorProxy-Authorizationheader, rather than by a Kong authentication plugin. - The upstream response can vary by caller.
Routes where a Kong authentication plugin identifies the Consumer aren’t affected by this issue.
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 |
Kong AI Gateway 2.3 isn’t impacted.
Contact
If you have questions or need help, open a case with Kong Support or email support@konghq.com.