Quick answers
- Is CVE-2026-14916 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14916 being exploited in the wild.
- How severe is CVE-2026-14916?
- Informational severity, published 16 September 2026.
- Which products and versions are affected?
- Kong API Gateway Enterprise <UNKNOWN>.
- Is there a fix for CVE-2026-14916?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-14916 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-14916?
- Check whether you run Kong API Gateway Enterprise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is a JWT algorithm confusion / signature verification vulnerability affecting Kong's MCP OAuth2 and DataKit integrations. The vulnerable code does not properly validate that the JWT signing algorithm matches the type of key used for verification, a classic JWT bypass technique. An unauthenticated remote attacker can craft a malicious JWT token that is incorrectly accepted as valid, leading to authentication bypass. The vulnerability allows potential compromise of confidentiality, integrity, and availability. Patch availability should be checked against Kong's official changelog and security advisories.
Affected products
- Kong API Gateway Enterprise <UNKNOWN>
Timeline
- 2026-09-16: disclosed