Identity Services EngineApplication · Cisco

CVE-2026-20190

HIGH · 7.5 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in Cisco ISE and ISE-PIC could allow an unauthenticated, remote attacker to view sensitive information on an affected device. This vulnerability is due to improper authorization checks when a resource is accessed. An attacker could exploit this vulnerability by sending crafted traffic to an affected device. A successful exploit could allow the attacker to gain access to sensitive information, including hashed credentials that could be used in future attacks.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an improper authorization vulnerability in Cisco ISE and ISE-PIC that allows unauthenticated remote attackers to bypass authorization checks and access sensitive resources. The attacker can view sensitive information including hashed credentials by sending specially crafted traffic to the affected device.

MitigationApply the Cisco patch for CVE-2026-20190 when available. If immediate patching is not possible, restrict network access to Cisco ISE management interfaces using firewall rules or ACLs to limit exposure to untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Identity Services EngineApplication
Affected:= 3.4.0= 3.5.0
Identity Services Engine Passive Identity ConnectorApplication
Affected:= 3.4.0= 3.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco ISE version
    Log into the ISE admin UI, navigate to Administration > System > Licensing, or run 'show version' command via CLI to confirm the installed ISE version
    Affected if Version is 3.4.0 or 3.5.0
  2. Identify ISE-PIC version
    If ISE-PIC is deployed, log into its admin interface or run 'show version' via CLI to confirm the installed PIC version
    Affected if Version is 3.4.0 or 3.5.0
  3. Assess management interface exposure
    Review network configuration to determine if Cisco ISE management ports (default 443, 8443) are accessible from outside the trusted network, check firewall rules and ACLs protecting the ISE management interface
    Affected if Management interface is reachable from untrusted or external networks
  4. Review access logs for anomalies
    Examine ISE authentication and access logs for unusual unauthenticated requests, especially those targeting sensitive endpoints or credential stores, look for unexpected IP sources
    Affected if Logs show unauthorized access attempts or successful unauthenticated queries to sensitive resources

Environment is affected if running Cisco ISE or ISE-PIC version 3.4.0 or 3.5.0 with management interfaces exposed to untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Cisco patch for CVE-2026-20190 when available. If immediate patching is not possible, restrict network access to Cisco ISE management interfaces using firewall rules or ACLs to limit exposure to untrusted networks.

Fix this in Identity Services Engine Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20190 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-20190 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data