CVE-2026-14917

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 49% 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 SAML authentication bypass vulnerability affects the Kong SAML plugin when the validate_assertion_signature option is explicitly set to false. This option is enabled by default. When disabled, the plugin may extract the SAML identity from an unsigned assertion and authenticate the user without verifying a valid cryptographic signature.

As a result, an unauthenticated remote attacker may be able to submit a crafted SAML response and impersonate arbitrary users, including administrators

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
51%
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/#3-15-0-3

Vendor Advisories for CVE-2026-14917(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 18× in last 7d / 18× 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-19 19:45 UTCEG score recompute
  2. 2026-09-19 19:45 UTCGHSA enrichment
  3. 2026-09-19 07:30 UTCEG score recompute
  4. 2026-09-19 07:30 UTCGHSA enrichment
  5. 2026-09-18 19:27 UTCEPSS rescore
  6. 2026-09-18 19:14 UTCGHSA enrichment
  7. 2026-09-18 15:28 UTCGHSA enrichment
  8. 2026-09-18 03:12 UTCEG score recompute
  9. 2026-09-18 03:12 UTCGHSA enrichment
  10. 2026-09-17 14:57 UTCGHSA enrichment
  11. 2026-09-17 02:42 UTCGHSA enrichment
  12. 2026-09-16 14:24 UTCEG score recompute
  13. 2026-09-16 14:24 UTCGHSA enrichment
  14. 2026-09-16 13:41 UTCEG score recompute
  15. 2026-09-16 13:41 UTCGHSA enrichment
  16. 2026-09-16 10:26 UTCEG score recompute
  17. 2026-09-16 10:12 UTCEG score recompute
  18. 2026-09-16 10:11 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-14917?
CVE-2026-14917 is a high vulnerability published on September 16, 2026. A SAML authentication bypass vulnerability affects the Kong SAML plugin when the validateassertionsignature option is explicitly set to false. This option is enabled by default. When disabled, the plugin may extract the SAML identity from an unsigned assertion and authenticate the user without…
When was CVE-2026-14917 disclosed?
CVE-2026-14917 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-14917 actively exploited?
CVE-2026-14917 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 48.5% of all scored CVEs.
What is the CVSS score of CVE-2026-14917?
CVE-2026-14917 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-14917?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14917, 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-14917

Explore →

Is Your Infrastructure Affected by CVE-2026-14917?

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