CVE-2026-92545
A cached response could cross gateway hostnames
Kong · Kong AI Gateway proxy response cache
First documented disclosure · Review checkpoint
Summary
The proxy cache omitted the hostname when identifying a cached response. A client could receive data generated for a different host.
Severity and exploitation evidence
High · 8.7/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 proxy cache omitted the hostname when identifying a cached response.
Conditions required
Distinct hostnames shared the affected cache configuration.
Potential impact
A client could receive data generated for a different host.
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 ·