A JWT signature verification vulnerability affects Kong components that perform JWT validation for MCP OAuth2 or DataKit integrations inside Kong API Gateway Enterprise. The affected code does not properly validate that the JWT signing algorithm is compatible with the type of key used for verification.
As a result, an unauthenticated remote attacker may be able to craft a forged JWT that is incorrectly accepted as valid, leading to authentication bypass and potential compromise of confidentiality, integrity, and availability.
Metrics
Affected Vendors & Products
References
| Link | Providers |
|---|---|
| https://developer.konghq.com/gateway/changelog/ |
|
History
Thu, 17 Sep 2026 02:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Kong
Kong kong Enterprise Gateway |
|
| Vendors & Products |
Kong
Kong kong Enterprise Gateway |
Wed, 16 Sep 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 16 Sep 2026 10:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | A JWT signature verification vulnerability affects Kong components that perform JWT validation for MCP OAuth2 or DataKit integrations inside Kong API Gateway Enterprise. The affected code does not properly validate that the JWT signing algorithm is compatible with the type of key used for verification. As a result, an unauthenticated remote attacker may be able to craft a forged JWT that is incorrectly accepted as valid, leading to authentication bypass and potential compromise of confidentiality, integrity, and availability. | |
| Title | Kong API Gateway Enterprise: JWT Algorithm-Confusion | |
| Weaknesses | CWE-241 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: Kong
Published: 2026-09-16T10:11:15.556Z
Updated: 2026-09-16T13:26:46.569Z
Reserved: 2026-07-07T07:14:53.612Z
Link: CVE-2026-14916
Updated: 2026-09-16T13:26:43.516Z
Status : Awaiting Analysis
Published: 2026-09-16T11:16:40.503
Modified: 2026-09-18T19:07:38.320
Link: CVE-2026-14916
No data.