Skip to main content
VulnerabilityPublished

CVE-2026-14917: Kong Enterprise Gateway · Authentication bypass using an alternate path or channel

Affects Kong Enterprise GatewaySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.7 High · fixed in 3.15.0.3 : patch Kong Enterprise Gateway soon.

Data as of 30 Oct 2026, 20:25 UTC

CVSS 4.0 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.15.0.3, 3.14.0.12, 3.13.0.9 +3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
KongKong Enterprise GatewayAffected
  • >=3.15.0.0 <3.15.0.3
Fixed in
  • 3.15.0.3
KongKong Enterprise GatewayAffected
  • >=3.14.0.0 <3.14.0.12
Fixed in
  • 3.14.0.12
KongKong Enterprise GatewayAffected
  • >=3.13.0.0 <3.13.0.9
Fixed in
  • 3.13.0.9
KongKong Enterprise GatewayAffected
  • >=3.12.0.0 <3.12.0.10
Fixed in
  • 3.12.0.10
KongKong Enterprise GatewayAffected
  • >=3.10.0.0 <3.10.0.17
Fixed in
  • 3.10.0.17
KongKong Enterprise GatewayAffected
  • >=3.4.0.0 <3.4.3.29
Fixed in
  • 3.4.3.29

AI-suggested

The vulnerability arises only when the validate_assertion_signature option is explicitly set to false, which is not the default configuration. Therefore, ensuring this option remains enabled (the default) mitigates the risk. Users should verify their configuration to confirm that validate_assertion_signature is not disabled.

Description

A SAML authentication bypass vulnerability affects the Kong SAML plugin when the validate_assertion_signature option is explicitly set to false. This option is enabled by default. When disabled, the plugin may extract the SAML identity from an unsigned assertion and authenticate the user without verifying a valid cryptographic signature. As a result, an unauthenticated remote attacker may be able to submit a crafted SAML response and impersonate arbitrary users, including administrators

References

Community reviews

Loading reviews…