Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify Kong gateway with SAML signature validation disabled
-
DeliveryCraft SAML response with unsigned admin assertion
-
ExploitSubmit to SAML consumer endpoint
-
ExecutionPlugin extracts identity, skips signature check
-
PersistAuthenticate as impersonated administrator
-
ImpactAccess protected downstream APIs and data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Alternate path authentication
|
| Exploitation Conditions | Exploitation requires the Kong SAML plugin to be in use AND the validate_assertion_signature option to be EXPLICITLY set to false. This is the critical gate: the option is enabled (true) by default, so default configurations are NOT exploitable - only deployments where an operator deliberately disabled assertion-signature validation are affected. When that condition holds, no further prerequisites apply: a remote unauthenticated attacker (AV:N/PR:N/UI:N/AC:L) can submit a crafted SAML response with an unsigned assertion and impersonate arbitrary users including administrators. The limiting factor is entirely the non-default configuration; there is no required user interaction or authentication. |
| Impact | This is a genuine authentication-bypass flaw (CWE-288) but its real-world risk is strongly gated by a non-default configuration. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, subsequent-system SC:H) confirms a remote, unauthenticated, low-complexity network vector against the SAML plugin - signals that in isolation read as critical. The decisive limiter, however, is stated plainly in the description: the flaw only manifests when validate_assertion_signature is EXPLICITLY set to false, and that option is enabled (true) by default. So default deployments are NOT vulnerable, which materially lowers the population at risk versus the raw pre-auth score. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no public exploit identified at time of analysis and no evidence of active or automatable exploitation. Net: treat as a real, patch-worthy authentication bypass for the subset of tenants that disabled signature validation, but it is not a blanket-critical, mass-exploitable issue - the configuration gate makes it targeted rather than widespread. Note also a modeling tension worth verifying with the vendor: the vendor 4.0 vector records only subsequent confidentiality (SC:H) with SI:N/SA:N, yet the description says an attacker can impersonate administrators, which would normally imply an integrity impact on protected downstream resources as well. |
| Exploit ScenarioDerived | An operator has disabled validate_assertion_signature on the Kong SAML plugin. A remote unauthenticated attacker crafts a SAML response containing an unsigned assertion that names an administrator as the subject and submits it to the gateway's SAML assertion consumer endpoint; the plugin extracts the identity without verifying any cryptographic signature and authenticates the attacker as that admin. No public POC was provided, but exploitation is low-complexity given the missing signature check. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 16, 2026
SAML authentication bypass in Kong Enterprise Gateway allows an unauthenticated remote attacker to impersonate arbitrary users, including administrators, by submitting a crafted SAML response containing an unsigned assertion. Exploitation is strictly gated by a non-default configuration: the Kong SAML plugin's validate_assertion_signature option must have been explicitly set to false, since it defaults to true - default deployments are not affected. No public exploit code has been identified at time of analysis and the flaw is not listed in CISA KEV; patch status is Vendor-released patch: Kong Gateway 3.15.0.3.
RemediationAI
Upgrade to Kong Gateway 3.15.0.3 (Vendor-released patch), documented in the Kong Gateway changelog at https://developer.konghq.com/gateway/changelog/#3-15-0-3, and re-audit every Kong SAML plugin configuration to ensure validate_assertion_signature is true or simply omitted so the secure default applies. Where an upgrade cannot be scheduled immediately, the effective compensating control is to re-enable assertion signature validation on all SAML plugin instances; the trade-off is that any identity provider currently feeding unsigned assertions will start failing authentication until it is configured to sign responses, so validate the IdP signing certificate and metadata before flipping the flag in production. As a secondary containment measure for deployments that must temporarily tolerate unsigned assertions, restrict plugin-protected routes to trusted network ranges or add a pre-authentication gateway/WAF rule requiring a signed SAMLResponse envelope, accepting the added latency and the risk that the WAF rule is bypassed by encoding tricks. After remediation, review Kong access and audit logs for SAML logins originating from unexpected source addresses or mapping to privileged identities during the exposure window, since a successful bypass would appear as a normal authenticated session.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the Kong SAML plugin, which implements SAML 2.0 service-provider authentication for Kong Enterprise Gateway (CPE cpe:2.3:a:kong:kong_enterprise_gateway:*:*:*:*:*:*:*:*). Root cause is CWE-288 (Authentication Bypass Using an Alternate Path or Channel): when the validate_assertion_signature configuration flag is set to false, the plugin accepts an unsigned SAML assertion as the source of user identity and issues an authenticated session without ever verifying a cryptographic signature over the assertion. Because SAML identity is attacker-controllable in an unsigned response, an attacker can set arbitrary NameID/attribute values and be mapped to any principal the plugin would normally trust, up to and including administrators. The correct gate is enforced by the option's default value of true - the vulnerable code path is only reachable when an operator has deliberately disabled signature validation, typically as a troubleshooting measure or to interoperate with a non-conforming identity provider. The CVSS 4.0 vector records PR:N/UI:N (no authentication, no user interaction) and subsequent-system high confidentiality scope, and our independent assessment (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) confirms a fully remote, pre-auth bypass that compromises the confidentiality and integrity of downstream protected resources once the non-default setting is in place.
Know when Kong gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Remote pre-auth bypass (AV:N/AC:L/PR:N/UI:N); scope change (S:C) as gateway auth grants access to separately-protected downstream resources; admin impersonation yields C:H/I:H, A:N.
Primary rating from Vendor (Kong).
CVSS VectorVendor: Kong
DescriptionCVE.org
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
Executive ViewAI
Kong Enterprise Gateway deployments that have explicitly disabled SAML assertion signature validation are exposed to a full authentication bypass, allowing a remote attacker to take on the identity of any user in the platform, including administrators. The condition is not present in default configurations - the setting in question defaults to its secure value - so exposure is limited to organizations that deliberately changed it, but for those organizations the potential impact includes privileged access to protected systems and data. Leadership should confirm whether the affected setting has been altered anywhere in the environment and prioritize remediation accordingly.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
The official kong docker images before 1.0.2-alpine (Alpine specific) contain a blank password for a root user. Rated cr
Signature-verification bypass in Kong API Gateway Enterprise lets an unauthenticated remote attacker present a forged JW
SQL injection in Kong Gateway (Enterprise and Open Source) Hybrid Mode clustering logic allows an attacker who can reach
A vulnerability was found in Konga 2.8.3 on Kong. Rated medium severity (CVSS 5.9), this vulnerability is remotely explo
Cross-site scripting (XSS) vulnerability in the phptemplate_preprocess_node function in template.php in the Inf08 theme
EUVD-2026-80387
GHSA-p8wp-m49r-5g58
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB