Skip to main content

Kong Enterprise Gateway EUVDEUVD-2026-80389

| CVE-2026-14916 HIGH
Improper Handling of Unexpected Data Type (CWE-241)
2026-09-16 Kong GHSA-5qvf-77w7-x85r
7.7
CVSS 4.0 · Vendor: Kong
Share

Severity by source

Vendor (Kong) PRIMARY
7.7 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
vuln.today AI
10.0 CRITICAL

Unauthenticated network-reachable JWT forgery (PR:N/UI:N/AC:L); scope change (S:C) as the gateway flaw compromises protected backends, granting read and impersonation-based write (C:H/I:H), availability not established (A:N).

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

Primary rating from Vendor (Kong).

CVSS VectorVendor: Kong

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
X

Lifecycle Timeline

3
Patch available
Sep 16, 2026 - 11:03 EUVD
Analysis Generated
Sep 16, 2026 - 11:01 vuln.today
CVE Published
Sep 16, 2026 - 10:11 cve.org
HIGH 7.7

DescriptionCVE.org

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.

AnalysisAI

Signature-verification bypass in Kong API Gateway Enterprise lets an unauthenticated remote attacker present a forged JWT that the gateway accepts as valid, defeating token-based authentication for the MCP OAuth2 and DataKit integration code paths. The vulnerable logic fails to confirm that the JWT's declared signing algorithm is compatible with the key type actually used for verification, so an attacker who can reach a protected endpoint that relies on these integrations can slip through as an authenticated principal; the independent assessment scopes the impact to the backend resources the gateway protects (C:H/I:H under a changed-scope CVSS:3.1 vector) rather than to the gateway host itself. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Requires the Kong API Gateway Enterprise deployment to be configured with the MCP OAuth2 or DataKit integration code paths that perform JWT validation - these specific, relatively new integrations are what contain the vulnerable verification logic, so gateways not using them are not exposed. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment This is a genuine unauthenticated auth-bypass primitive, but its real-world priority is strongly gated by configuration. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation Upgrade Kong API Gateway Enterprise to the release identified in the vendor changelog (https://developer.konghq.com/gateway/changelog/) as containing the fix for CVE-2026-14916; the supplied data does not include an exact patched version number, so read the changelog entry rather than assuming one. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours, inventory every Kong API Gateway Enterprise deployment and determine which instances have MCP OAuth2 or DataKit JWT validation enabled, then restrict network reachability to those protected endpoints to trusted source ranges or internal segments only; apply an upstream proxy or WAF rule that rejects tokens whose declared algorithm does not match the expected signing algorithm, and enable verbose authentication logging on the affected code paths. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

EUVD-2026-80389 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy