DE EN IT

~/exploited / cve-2026-76460

CVE-2026-76460: Cisco Identity Services Engine

According to CISA this vulnerability is already used in attacks (added on 16 September 2026).

Key facts

CVECVE-2026-76460
VendorCisco — Identity Services Engine
VulnerabilityCisco Identity Services Engine Incorrect Use of Privileged APIs Vulnerability
Added16 September 2026
Deadline (US agencies)19 September 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score10.0 (critical) · CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Attack over the network, complexity: low, privileges: none needed, user interaction: none
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 75.6%. Higher than 99.5% of all scored vulnerabilities (as of 18 November 2026). A high value means attacks are very likely and often already widespread.
Weakness type (CWE)CWE-648
Affected versionsidentity services engine 3.1.0
identity services engine 3.2.0
identity services engine 3.3.0
identity services engine 3.4.0
identity services engine 3.5.0
identity services engine passive identity connector 3.1.0
identity services engine passive identity connector 3.2.0
identity services engine passive identity connector 3.3.0
and 1 more

Description (NVD)

A vulnerability in an API of Cisco Identity Services Engine (ISE) could allow an unauthenticated, remote attacker to bypass authentication. This vulnerability is due to insufficient authentication control on an API endpoint. An attacker could exploit this vulnerability by sending a crafted request to an affected API endpoint. A successful exploit could allow the attacker to gain unauthorized access to the affected device by bypassing the web-based management interface.

Patches and vendor advisories

Description (CISA)

Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC) contain an incorrect use of privileged APIs vulnerability that could allow an unauthenticated, remote attacker to gain unauthorized access to the affected device by bypassing the web-based management interface.

Required action (CISA)

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

What admins should do now

  1. Affected? Check whether Cisco Identity Services Engine is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 16 September 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).