Security Advisory: CVE-2026-96437

Uses: Kong Gateway
Severity
High
Published
2026-11-10
Kong Gateway Enterprise
Fixed versions
  • 3.13.0.12
  • 3.14.0.11
  • 3.15.0.4
Affected versions
  • 3.13.0.0 to < 3.13.0.12
  • 3.14.0.0 to < 3.14.0.11
  • 3.15.0.0 to < 3.15.0.4
  • 3.16.0.0 to < 3.16.0.1

CVE

Description

Severity

Affects Kong

CVE-2026-96437 ai-azure-content-safety input guard bypass for large request bodies High (CVSS 4.0: 8.2) Yes

A high-severity input guard bypass in the ai-azure-content-safety plugin affects Kong Gateway Enterprise 3.13 to 3.16.

CVE-2026-96437

The ai-azure-content-safety plugin in affected versions of Kong Gateway Enterprise may not inspect the prompt in a request whose body exceeds the gateway’s in-memory request body buffer (client_body_buffer_size). In that case the plugin skips content-safety evaluation and forwards the unfiltered prompt to the upstream model.

A caller may therefore bypass input content-safety inspection by sending a larger request body. The request isn’t rejected and no error is returned. Shorter prompts continue to be inspected, so the control appears to be working while longer prompts, such as pasted documents, retrieved context, or long conversation history, aren’t inspected.

  • Severity: High
  • CVSS v4.0 score: 8.2
  • Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
  • Exploitation: No evidence of exploitation in the wild at this time. Reported through Kong’s HackerOne bug bounty program with a working proof-of-concept; not publicly disclosed.

Am I affected?

You should consider a Kong Gateway Enterprise deployment potentially affected if all of the following are true:

  • ai-azure-content-safety is enabled with guarding_mode set to INPUT (the default) or BOTH.
  • Callers can submit request bodies larger than the gateway’s request body buffer.

With guarding_mode set to BOTH, output inspection still applies. Requests below the buffer size are inspected normally. Kong AI Gateway 2.x isn’t affected.

Mitigation

If you can’t upgrade yet, reject request bodies that don’t fit in the buffer so they never reach the upstream without inspection. Set nginx_http_client_max_body_size to the same value as nginx_http_client_body_buffer_size, sized for your largest legitimate prompt (for example 1m for both), or enforce the same limit with the request-size-limiting plugin. Raising client_body_buffer_size alone isn’t sufficient: it only raises the size above which requests aren’t inspected.

Patches

The vulnerability is addressed by applying the patch appropriate for your version:

Impacted supported versions of Kong Gateway Enterprise

Patch

3.13.0.0 - < 3.13.0.12 3.13.0.12
3.14.0.0 - < 3.14.0.11 3.14.0.11
3.15.0.0 - < 3.15.0.4 3.15.0.4

Contact

If you have questions or need help, open a case with Kong Support or email support@konghq.com.

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!