CVE Tools

CVE-2026-20234

Cisco Identity Services Engine Hardening Release - Insuffiencently Protected Credential Vulnerabilities

Public exploit available. Not confirmed exploited in the wild yet. No fix published yet.

Published Updated Sources: CVE.org, NVD

What to do

No fixed build or workaround is published yet. Limit exposure and watch for a patch.

Steps

Written by AI from the record
  1. Confirm whether your organization runs Cisco Identity Services Engine software or Cisco ISE Passive Identity Connector, including appliances managed by a provider.
  2. Ask Cisco or your IT provider whether your installed release is affected by CVE-2026-20234 and whether any hardening release is available.
  3. No fixed version has been provided in the available findings; obtain Cisco’s supported remediation guidance before making changes.
  4. Until remediation is available, restrict administrative access to trusted staff and review privileged account activity for unexpected changes.

What it is

From the CVE record

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-20234 are related to insufficiently protected credentials issues that are grouped under the Common Weakness Enumeration (CWE) Pillar CWE-522.

In plain language

Written by AI from the record

A critical credential-protection flaw affects Cisco Identity Services Engine software and Cisco ISE Passive Identity Connector; businesses using either should act now because public attack code is available.

CWE-522 insufficiently protected credentials vulnerabilities in Cisco Identity Services Engine software and Cisco ISE Passive Identity Connector can enable a logged-in attacker to compromise confidentiality, integrity, and availability across security scopes.

If you're affected

  • Network access control takeover
  • Credential exposure
  • Policy changes
  • Service disruption
  • Ransomware risk

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS28th
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

0 sources with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

0.4% chance of exploitation activity in the next 30 days, which ranks it in the 28th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 1 day, from the signal feeds we watch.

  1. Record updatedrecord updated
  2. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

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

Scored 9.9 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Cisco, not every advisory. This one: public exploit.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store