A high-severity vulnerability in the request-callout plugin affects Kong Gateway Enterprise and Kong AI Gateway.
Security Advisory: CVE-2026-123041
- 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-123041 |
request-callout cache key omits callout headers that aren’t sent by the client
|
High (CVSS 4.0: 8.2) | Yes |
CVE-2026-123041
The request-callout plugin in Kong Gateway Enterprise and Kong AI Gateway can cache the responses to its callouts. The cache key includes a callout request header only when the client’s own request carries a header with the same name. A callout header whose value comes from another source, such as a differently named client header, a query parameter, the request body, or custom Lua code, is left out of the cache key.
Where such a header identifies the caller, for example a callout that builds an Authorization header from a client-supplied token header, callers with different values share a single cache entry. This can lead to disclosure of the first caller’s data.
- 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. Identified internally by Kong.
Am I affected?
You should consider a Kong Gateway Enterprise or Kong AI Gateway deployment potentially affected if all of the following are true:
request-calloutis enabled on a Route or Service with callout caching enabled (cache.strategyset tomemoryorredis).- A callout sets a request header that identifies the caller, and its value comes from a differently named client header, a query parameter, the request body, or custom Lua code.
- Requests on the Route aren’t associated with a Kong Consumer.
Callout caching is disabled by default (cache.strategy is off). Where a Kong authentication plugin identifies the Consumer, cache entries are kept separate per Consumer and the issue doesn’t apply.
Mitigation
If it isn’t possible to update, disable callout caching (set cache.strategy to off), or derive each caller-identifying callout header from a client header with the same name (for example, Authorization to Authorization). Alternatively, identify callers with a Kong authentication plugin.
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.