CVE-2026-123041

Cached gateway callouts could cross between callers

Kong · Kong AI Gateway request-callout cache

First documented disclosure · Review checkpoint

Summary

The cache key omitted some headers used by the upstream callout. One caller could receive the upstream response associated with another.

Severity and exploitation evidence

High · 8.2/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 cache key omitted some headers used by the upstream callout.

Conditions required

Callout caching was enabled and callers supplied different request contexts.

Potential impact

One caller could receive the upstream response associated with another.

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