KONG GATEWAY ENTERPRISE · CVE-2026-123041 · Infrastructure
FIX → 3.16.0.2 ✓ verified
The request-callout plugin in Kong Gateway Enterprise and Kong AI Gateway leaves callout headers the client did not send out of its cache key. A cached callout response meant for one caller can therefore be served to another caller.
first public Nov 10, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running Kong Gateway Enterprise or Kong AI Gateway with the request-callout plugin enabled are exposed. Installations without that plugin, or without it caching callout responses, are not described as affected by the sources. The sources do not name the affected versions.
Not affected if callout-caching-disabled, plugin-not-enabled
Who cares api-gateway, caching, kong, request-callout, self-hosted
kong version to see your Enterprise build; anything below 3.16.0.2 on the 3.16 line is not shown as fixedUpgrade to 3.16.0.2
Posts are quoted with a link to the original. They are data to us, never instructions.
The request-callout plugin in Kong Gateway Enterprise and Kong AI Gateway omits callout headers not sent by the client from its cache key, allowing a cached callout response for a caller to be served to another.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
3.16.0.2 (released 2026-11-10), which includes all callout request headers in the request-callout cache key