CVE-2026-14916

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this week
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.7
EG Score
7.7(medium)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity77% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

Kong Gateway changelog - Kong Gateway | Kong Docs

https://developer.konghq.com/gateway/changelog/

Vendor Advisories for CVE-2026-14916(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-18 19:14 UTCGHSA enrichment
  3. 2026-09-18 15:06 UTCGHSA enrichment
  4. 2026-09-18 02:56 UTCEG score recompute
  5. 2026-09-18 02:56 UTCGHSA enrichment
  6. 2026-09-17 14:47 UTCGHSA enrichment
  7. 2026-09-17 02:36 UTCGHSA enrichment
  8. 2026-09-16 14:24 UTCEG score recompute
  9. 2026-09-16 14:24 UTCGHSA enrichment
  10. 2026-09-16 13:41 UTCEG score recompute
  11. 2026-09-16 13:40 UTCGHSA enrichment
  12. 2026-09-16 11:26 UTCEG score recompute
  13. 2026-09-16 10:34 UTCEG score recompute
  14. 2026-09-16 10:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-14916?
CVE-2026-14916 is a high vulnerability published on September 16, 2026. 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…
When was CVE-2026-14916 disclosed?
CVE-2026-14916 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14916 actively exploited?
CVE-2026-14916 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 49.6% of all scored CVEs.
What is the CVSS score of CVE-2026-14916?
CVE-2026-14916 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-14916?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14916, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-14916

Explore →

Is Your Infrastructure Affected by CVE-2026-14916?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs