Kong API Gateway Enterprise: JWT Algorithm-Confusion
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.15.0.3, 3.14.0.12, 3.13.0.9, 3.12.0.10, 3.10.0.17, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Kong Kong Enteprise Gateway
From 3.15.0.0 · fixed in 3.15.0.3; From 3.14.0.0 · fixed in 3.14.0.12; From 3.13.0.0 · fixed in 3.13.0.9; From 3.12.0.0 · fixed in 3.12.0.10; From 3.10.0.0 · fixed in 3.10.0.17; From 3.4.0.0 · fixed in 3.4.3.29