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.
CVE-2026-6338
This medium-severity CVE scores 4.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.9
- EG Score
- 4.9(medium)
- EPSS
- 16.6%
- KEV
- Not listed
Published
June 11, 2026
Last Modified
June 11, 2026
Advisory Details (1)
Auto-updated Jun 15, 2026Vendor Advisories for CVE-2026-6338(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Frequently asked(5)
What is CVE-2026-6338?
When was CVE-2026-6338 disclosed?
Is CVE-2026-6338 actively exploited?
What is the CVSS score of CVE-2026-6338?
How do I remediate CVE-2026-6338?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-6338
Is Your Infrastructure Affected by CVE-2026-6338?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.