Kong Enteprise Gateway
Kong API Gateway Enterprise: JWT Algorithm-Confusion
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.15.0.0, < 3.15.0.3
- >= 3.14.0.0, < 3.14.0.12
- >= 3.13.0.0, < 3.13.0.9
- >= 3.12.0.0, < 3.12.0.10
- >= 3.10.0.0, < 3.10.0.17
- >= 3.4.0.0, < 3.4.3.29
Fixed in 3.15.0.3, 3.14.0.12, 3.13.0.9, 3.12.0.10, 3.10.0.17, 3.4.3.29
Mitigation
Upgrade Kong Enteprise Gateway to 3.15.0.3 or 3.14.0.12 or 3.13.0.9 or 3.12.0.10 or 3.10.0.17 or 3.4.3.29 or later.
References
- Release notes developer.konghq.com/gateway/changelog
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.