CVE-2026-6338
HTTP request smuggling in Kong Enteprise Gateway
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- 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
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- 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