CVE-2026-6338

MEDIUMPre-NVD 4.94.9—
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
4.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.9
EG Score
4.9(medium)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity49% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
16.8%
KEV
Not listed

Published

June 11, 2026

Last Modified

June 11, 2026

Advisory Details (1)

Auto-updated Jun 15, 2026
No patch confirmed yet.
generic

Home

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

Vendor 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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 67× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 03:22 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 23:29 UTCGHSA enrichment
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-15 19:51 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-14 18:25 UTCGHSA enrichment
  17. 2026-07-13 22:31 UTCEPSS rescore
  18. 2026-07-13 19:18 UTCGHSA enrichment
  19. 2026-07-13 06:13 UTCEPSS rescore
  20. 2026-07-13 06:13 UTCEPSS rescore
  21. 2026-07-12 20:31 UTCGHSA enrichment
  22. 2026-07-12 05:46 UTCEPSS rescore
  23. 2026-07-11 20:20 UTCGHSA enrichment
  24. 2026-07-11 08:27 UTCEPSS rescore
  25. 2026-07-11 08:27 UTCEPSS rescore
Show 75 more
  1. 2026-07-10 21:41 UTCGHSA enrichment
  2. 2026-07-09 23:04 UTCGHSA enrichment
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-09 19:10 UTCEPSS rescore
  5. 2026-07-09 00:26 UTCGHSA enrichment
  6. 2026-07-08 15:16 UTCEPSS rescore
  7. 2026-07-08 15:16 UTCEPSS rescore
  8. 2026-07-08 01:50 UTCGHSA enrichment
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-07 13:46 UTCEPSS rescore
  11. 2026-07-07 03:10 UTCGHSA enrichment
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-05 12:02 UTCGHSA enrichment
  17. 2026-07-05 02:31 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 13:25 UTCGHSA enrichment
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-03 14:48 UTCGHSA enrichment
  23. 2026-07-02 14:50 UTCGHSA enrichment
  24. 2026-07-01 16:13 UTCGHSA enrichment
  25. 2026-07-01 15:07 UTCEPSS rescore
  26. 2026-06-30 23:22 UTCEPSS rescore
  27. 2026-06-30 17:37 UTCGHSA enrichment
  28. 2026-06-29 18:53 UTCGHSA enrichment
  29. 2026-06-29 14:06 UTCEPSS rescore
  30. 2026-06-28 18:25 UTCGHSA enrichment
  31. 2026-06-28 14:07 UTCEPSS rescore
  32. 2026-06-28 04:56 UTCEPSS rescore
  33. 2026-06-27 19:49 UTCGHSA enrichment
  34. 2026-06-27 03:08 UTCEPSS rescore
  35. 2026-06-26 21:13 UTCGHSA enrichment
  36. 2026-06-25 22:37 UTCGHSA enrichment
  37. 2026-06-25 13:50 UTCEPSS rescore
  38. 2026-06-25 00:00 UTCGHSA enrichment
  39. 2026-06-24 14:05 UTCEPSS rescore
  40. 2026-06-24 01:23 UTCGHSA enrichment
  41. 2026-06-23 21:33 UTCEPSS rescore
  42. 2026-06-23 21:33 UTCEPSS rescore
  43. 2026-06-23 02:45 UTCGHSA enrichment
  44. 2026-06-22 14:25 UTCEPSS rescore
  45. 2026-06-22 14:25 UTCEPSS rescore
  46. 2026-06-22 04:00 UTCGHSA enrichment
  47. 2026-06-21 14:56 UTCEPSS rescore
  48. 2026-06-21 14:56 UTCEPSS rescore
  49. 2026-06-21 04:50 UTCGHSA enrichment
  50. 2026-06-21 01:59 UTCEPSS rescore
  51. 2026-06-21 01:59 UTCEPSS rescore
  52. 2026-06-20 06:02 UTCGHSA enrichment
  53. 2026-06-19 19:26 UTCEPSS rescore
  54. 2026-06-19 19:26 UTCEPSS rescore
  55. 2026-06-19 06:06 UTCGHSA enrichment
  56. 2026-06-18 17:52 UTCEPSS rescore
  57. 2026-06-18 17:52 UTCEPSS rescore
  58. 2026-06-18 07:02 UTCGHSA enrichment
  59. 2026-06-17 17:53 UTCEPSS rescore
  60. 2026-06-17 07:37 UTCGHSA enrichment
  61. 2026-06-16 17:53 UTCEPSS rescore
  62. 2026-06-16 09:01 UTCGHSA enrichment
  63. 2026-06-15 17:49 UTCEPSS rescore
  64. 2026-06-15 17:49 UTCEPSS rescore
  65. 2026-06-15 10:24 UTCGHSA enrichment
  66. 2026-06-14 23:18 UTCEPSS rescore
  67. 2026-06-14 11:47 UTCGHSA enrichment
  68. 2026-06-13 23:00 UTCEPSS rescore
  69. 2026-06-13 13:10 UTCGHSA enrichment
  70. 2026-06-12 23:12 UTCEPSS rescore
  71. 2026-06-12 23:12 UTCEPSS rescore
  72. 2026-06-12 14:33 UTCGHSA enrichment
  73. 2026-06-11 15:56 UTCEG score recompute
  74. 2026-06-11 15:56 UTCGHSA enrichment
  75. 2026-06-11 15:55 UTCNVD updateCVSS v3 → 4.9 · CVSS v4 → 4.9

Frequently asked(5)

What is CVE-2026-6338?
CVE-2026-6338 is a medium vulnerability published on June 11, 2026. 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.
When was CVE-2026-6338 disclosed?
CVE-2026-6338 was first published in the National Vulnerability Database on June 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6338 actively exploited?
CVE-2026-6338 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6338?
CVE-2026-6338 has a CVSS v3 base score of 4.9 (NVD).
How do I remediate CVE-2026-6338?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6338, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-6338

Explore →

Is Your Infrastructure Affected by CVE-2026-6338?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs