CVE Tools

CVE-2026-20130

Cisco Identity Services Engine Hardening Release - Improper Neutralization 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. Check whether your organization runs Cisco Identity Services Engine software or its Passive Identity Connector.
  2. Ask your Cisco support contact whether your installed release is affected by CVE-2026-20130; Cisco has not published fixed-version information.
  3. Limit access to the affected systems to only necessary administrators and networks until Cisco provides remediation.
  4. Watch Cisco security advisories for a fixed release and install it as soon as Cisco confirms one.

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-20130 are related to improper neutralization of special elements issues that are grouped under the Common Weakness Enumeration (CWE) Pillar CWE-74.

In plain language

Written by AI from the record

This is a critical flaw in Cisco Identity Services Engine software that may let an outsider take over affected systems, so small businesses using it should act now.

Network-reachable, unauthenticated improper neutralization of special elements (CWE-74) in Cisco Identity Services Engine Software and Cisco ISE Passive Identity Connector, with public exploit availability and critical CVSS 10.0 impact.

If you're affected

  • Identity system takeover
  • Sensitive identity data exposure
  • Unauthorized access changes
  • Business access outages

Exploitation

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

EPSS31st
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 31st percentile of scored CVEs.

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

Lifecycle

6 events over 2 days, 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:N/UI:N/S:C/C:H/I:H/A:H

Scored 10.0 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 NoneNo authentication required — anyone can exploit this
  • 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