As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC), engineering teams have conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by CVE-2026-20237 are related to improper input validation issues that are grouped under the Common Weakness Enumeration (CWE) Pillar CWE-20.
CVE-2026-20237
Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-16. a secondary CVSS source baseline 9.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.1
- EG Score
- 9.1(high)
- EG Risk
- 41(Track)EG Risk 41/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 computedSeverity91% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 26%
- KEV
- Not listed
Published
September 16, 2026
Last Modified
September 18, 2026
Advisory Details (1)
Auto-updated Sep 16, 2026Cisco Identity Services Engine Hardening Release: September 2026
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-hardening-ise-XU5EwX5TVendor Advisories for CVE-2026-20237(2)
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 27× in last 7d / 27× 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.
- 2026-09-19 02:14 UTCGHSA enrichment
- 2026-09-18 22:15 UTCEG score recompute
- 2026-09-18 22:15 UTCGHSA enrichment
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 18:18 UTCGHSA enrichment
- 2026-09-18 14:21 UTCEG score recompute
- 2026-09-18 14:21 UTCGHSA enrichment
- 2026-09-18 13:44 UTCEG score recompute
- 2026-09-18 13:44 UTCGHSA enrichment
- 2026-09-18 12:28 UTCGHSA enrichment
- 2026-09-18 08:31 UTCGHSA enrichment
- 2026-09-18 04:34 UTCEG score recompute
- 2026-09-18 04:34 UTCGHSA enrichment
- 2026-09-18 04:04 UTCEG score recompute
- 2026-09-18 04:04 UTCGHSA enrichment
- 2026-09-18 02:12 UTCGHSA enrichment
- 2026-09-17 22:15 UTCEG score recompute
- 2026-09-17 22:15 UTCGHSA enrichment
- 2026-09-17 18:18 UTCGHSA enrichment
- 2026-09-17 12:53 UTCGHSA enrichment
- 2026-09-17 08:50 UTCGHSA enrichment
- 2026-09-17 04:53 UTCGHSA enrichment
- 2026-09-17 00:56 UTCEG score recompute
- 2026-09-17 00:56 UTCGHSA enrichment
- 2026-09-16 20:31 UTCEG score recompute
Show 2 moreShow fewer
- 2026-09-16 20:09 UTCEG score recompute
- 2026-09-16 20:09 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-20237?
When was CVE-2026-20237 disclosed?
Is CVE-2026-20237 actively exploited?
What is the CVSS score of CVE-2026-20237?
How do I remediate CVE-2026-20237?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-20237
Is Your Infrastructure Affected by CVE-2026-20237?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.