CVE-2026-92443
Authenticated gateway responses could be reused across callers
Kong · Kong AI Gateway response caching
First documented disclosure · Review checkpoint
Summary
The caching plugins stored responses to requests carrying authorization credentials without adequate separation. Data served to an authenticated user could be returned to a different user.
Severity and exploitation evidence
High · 8.2/10 · CVSS 4.0. Severity source.
Exploitation not established: The reviewed advisory does not report malicious exploitation.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
The caching plugins stored responses to requests carrying authorization credentials without adequate separation.
Conditions required
A route cached a response to an authenticated request and another caller used that route.
Potential impact
Data served to an authenticated user could be returned to a different user.
Affected versions and configurations
Kong AI Gateway 2.2.0. Enterprise branch ranges are listed separately in the CNA record.
Fix and mitigation status
Kong AI Gateway 2.2.1.
Practical next steps
Upgrade AI Gateway to 2.2.1 and review the affected gateway configuration.
Operating lesson
Keep each authenticated response isolated to the caller and request that created it.
Evidence and limits
The CVE record was published on 2026-11-10.
Sources
- Kong release changelog
Primary source ·
- Kong CVE record
Primary source ·