Kong API Gateway Enterprise: JWT Algorithm-Confusion
Kong Enteprise Gateway
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Kong Kong Enteprise Gateway Linux |
| No fix yet |
Kong Enteprise Gateway
| Product | Affected | Fixed in |
|---|---|---|
| Kong Kong Enteprise Gateway Linux |
| No fix yet |
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.
From the CVE record · Kong
Kong API Gateway Enterprise components that validate JWTs for MCP OAuth2 or DataKit integrations do not properly check whether the signing algorithm is compatible with the verification key. An unauthenticated remote attacker may be able to submit a forged JWT that is accepted as valid, bypassing authentication.
Teams running Kong API Gateway Enterprise with MCP OAuth2 or DataKit integrations should check their deployments; affected versions were not specified.