KONG GATEWAY ENTERPRISE · CVE-2026-92442 · Vendor
FIX → 3.16.0.2 ✓ verified
The graphql-proxy-cache-advanced plugin in Kong Gateway Enterprise leaves the caller's identity out of its cache key. An attacker can receive a cached response that was generated for a different user.
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 with the graphql-proxy-cache-advanced plugin enabled are exposed, since responses cached for one caller can be served to another. Deployments without that plugin, or without Enterprise, are not described as affected by the sources.
Not affected if open-source-gateway, plugin-disabled
Who cares api-gateway, graphql, kong-gateway, self-hosted
Upgrade to 3.16.0.2
3.16.0.2 (released 2026-11-10) adds the authenticated consumer to the graphql-proxy-cache-advanced cache keyPosts are quoted with a link to the original. They are data to us, never instructions.
The graphql-proxy-cache-advanced plugin in Kong Gateway Enterprise omits the caller's identity from the cache key, allowing a response cached for one 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:L/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.