CVE-2026-92558

Different requests on one gateway route could share a cached response

Kong · Kong AI Gateway proxy cache key handling

First documented disclosure · Review checkpoint

Summary

The proxy cache did not reliably distinguish separators from data within its request key. A caller could receive cached data belonging to a different request.

Severity and exploitation evidence

Medium · 6.3/10 · CVSS 4.0. Severity source.

Exploitation not established: The reviewed advisory does not report malicious exploitation.

Exploitation evidence source

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 did not reliably distinguish separators from data within its request key.

Conditions required

Proxy caching was enabled on the affected route.

Potential impact

A caller could receive cached data belonging to a different request.

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