CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to Daily brief 2026-09-17
CRITICALCVE-2026-76460 +3exploitedupdatedNATOA1vulnerability

CVE-2026-76460 (+ CVE-2026-76423), Cisco Identity Services Engine: unauthenticated API authentication bypass to root, found while resolving a customer support case, no workaround beyond ACLs (CVSS 10.0)

Cisco confirms active exploitation of an unauthenticated ISE API bypass that can reach root, found while resolving a customer support case

Defender actions

  • Apply infrastructure ACLs to every Cisco ISE/ISE-PIC node today restricting management-plane access to required sources only, then patch to 3.1 Patch 12 / 3.2 Patch 11 / 3.3 Patch 12 / 3.4 Patch 7 / 3.5 Patch 4 (migrate off 3.0, which is past End of Software Maintenance) at the earliest window.
  • Review access.log on every ISE node (or pull a support bundle with debug logs for apigateway/access.log.*.gz) for suspicious usernames on the API endpoint, and cross-check firewall and network logs outside the ISE appliance for unexpected outbound transfers, because Cisco warns on-box evidence may be removed by an attacker who reaches root. Re-image any node where malicious activity is suspected and restore it from configuration backup, as Cisco recommends.

Analysis

Cisco disclosed CVE-2026-76460 (CVSS 3.1 10.0, AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H) on 2026-09-16: an unauthenticated, remote attacker can bypass authentication on an API endpoint of Cisco Identity Services Engine (ISE) and ISE Passive Identity Connector (ISE-PIC) due to insufficient authentication control, affecting every release "regardless of device configuration" (Cisco PSIRT, 2026-09-16). Cisco confirms the flaw was found while resolving a customer's TAC support case, not internal research, and states it is aware of active exploitation (Cisco PSIRT, 2026-09-16); a successful exploit bypasses the web-based management interface entirely and, per Cisco's own advisory, "threat actors may obtain command execution with root privileges" (Cisco PSIRT, 2026-09-16). There is no workaround; the only mitigation is restricting management-plane access via infrastructure ACLs. Fixed releases are 3.1 Patch 12, 3.2 Patch 11, 3.3 Patch 12, 3.4 Patch 7 and 3.5 Patch 4; Cisco ISE 3.0 has reached End of Software Maintenance and must migrate to a supported, fixed release (Cisco PSIRT, 2026-09-16). CISA added the flaw to its Known Exploited Vulnerabilities catalog the same day (CISA, 2026-09-16; CISA KEV JSON feed, 2026-09-16).

This CVE was part of a bundled disclosure of 15 distinct Cisco ISE advisories the same day (Cisco PSIRT, 2026-09-16). A sibling flaw, CVE-2026-76423 (CVSS 10.0, also unauthenticated and affecting every release "regardless of device configuration"), removes the same authentication boundary via a separate API endpoint, letting an attacker read or modify ISE configuration and identity data with administrative privileges; Cisco states it is "not aware of any public announcements or malicious use" of this second flaw as of disclosure, but it shares the same fixed-release schedule (Cisco PSIRT, 2026-09-16).

Triage: a legitimate administrative session against the ISE API originates from an authenticated, known management source; the discriminator here is that exploitation reaches the API without any authentication at all, so any successful request against the affected endpoint from outside expected management-plane sources is itself the signal, and because a root-level attacker can edit or delete access.log entries, an apparently clean on-box log is not evidence of an intact device. Cisco's guidance is to corroborate against firewall and network logs external to the ISE node for unexpected outbound uploads or downloads to unfamiliar IP addresses.

Cited evidence

The Cisco PSIRT is aware of active exploitation of this vulnerability. Cisco strongly recommends that customers upgrade to a fixed software release to remediate this vulnerability.

This vulnerability was found during the resolution of a Cisco Technical Assistance Center (TAC) support case.

Upon successful exploitation of this vulnerability, threat actors may obtain command execution with root privileges.

Cisco PSIRT 2026-09-16

Of the 21 vulnerabilities in total, 13 are rated critical. Based on the CVSS scores Cisco published, four vulnerabilities can be exploited remotely without authentication. (translated from Dutch)

Four vulnerabilities, CVE-2026-20130, CVE-2026-20192, CVE-2026-76423 and CVE-2026-76460, have a CVSS score of 10.0. (translated from Dutch)

NCSC-NL (NCSC-2026-0382) 2026-09-17

Updates2

Update

CVE-2026-76460 was one part of a much larger Cisco ISE hardening release the same day. NCSC-NL's advisory scopes 21 of the disclosed vulnerabilities and states: "Of the 21 vulnerabilities in total, 13 are rated critical. Based on the CVSS scores Cisco published, four vulnerabilities can be exploited remotely without authentication" (translated from Dutch) (NCSC-NL, 2026-09-17). Two further CVEs join the maximum-severity tier alongside the already-covered CVE-2026-76460 and CVE-2026-76423: "Four vulnerabilities, CVE-2026-20130, CVE-2026-20192, CVE-2026-76423 and CVE-2026-76460, have a CVSS score of 10.0" (translated from Dutch) (NCSC-NL, 2026-09-17); Cisco groups multiple underlying flaws sharing a CWE classification for a hardening release under one CVE ID, with the CVSS score representing the highest-scoring underlying flaw in each bundle. CERT-FR's combined advisory reports Cisco's statement that CVE-2026-76460 is actively exploited (CERT-FR, 2026-09-17). Cisco's advisory for CVE-2026-76423 and five further flaws says Cisco is not aware of malicious use of any of them (Cisco PSIRT, 2026-09-16), and its hardening advisory says the same of the flaws it covers except where noted (Cisco PSIRT hardening advisory, 2026-09-16). Cisco's hardening advisory marks the improper-access-control class covered by CVE-2026-20192 with the note that one vulnerability belonging to that class is known to be actively exploited, and points to Cisco's Identity Services Engine Authentication Bypass advisory for it (Cisco PSIRT hardening advisory, 2026-09-16). That advisory covers CVE-2026-76460 (Cisco PSIRT, 2026-09-16). CERT-FR also reports Cisco's statement that ISE 3.1 and 3.2, which leave support on 30 November 2027, have not received a fix for eight of the disclosed CVEs (CERT-FR, 2026-09-17). Cisco's hardening advisory places both trains in the Software Maintenance phase, where only fixes for critical vulnerabilities are included, and advises migrating to a supported release that includes all of the hardening fixes (Cisco PSIRT hardening advisory, 2026-09-16).

Correction

The 2026-09-18 text said no other CVE in the release was named exploited by any source. It also credited CERT-FR with saying that only CVE-2026-76460 is exploited, while CERT-FR reports Cisco's statement that CVE-2026-76460 is actively exploited (CERT-FR, 2026-09-17) and the exclusivity comes from Cisco's other advisories, which report no malicious use of the flaws they cover except where noted (Cisco PSIRT, 2026-09-16) (Cisco PSIRT hardening advisory, 2026-09-16). Cisco's hardening advisory notes that one vulnerability in the improper-access-control class covered by CVE-2026-20192 is known to be actively exploited and refers to its Identity Services Engine Authentication Bypass advisory for it (Cisco PSIRT hardening advisory, 2026-09-16), the advisory for CVE-2026-76460 (Cisco PSIRT, 2026-09-16). The same text said ISE 3.1 and 3.2 will not receive a fix at all for eight of the disclosed CVEs. CERT-FR reports only that those trains have not received a fix for them (CERT-FR, 2026-09-17), and Cisco says 3.1 and 3.2 now take only fixes for critical vulnerabilities (Cisco PSIRT hardening advisory, 2026-09-16). The eight are CVE-2026-20247, CVE-2026-20282, CVE-2026-20300 and CVE-2026-76424 through CVE-2026-76428 (CERT-FR, 2026-09-17). None of them is one of the four CVSS 10.0 flaws, which are fixed on every supported train including 3.1 Patch 12 and 3.2 Patch 11 (Cisco PSIRT hardening advisory, 2026-09-16) (Cisco PSIRT, 2026-09-16) (Cisco PSIRT, 2026-09-16). CERT-FR also notes that ISE-PIC is no longer sold and 3.4 is its last maintained release (CERT-FR, 2026-09-17). Where malicious activity is suspected, Cisco recommends re-imaging the affected nodes and restoring from configuration backup (Cisco PSIRT, 2026-09-16). The main text also described ISE as standard infrastructure across enterprise and public-sector networks without a source, and that sentence is removed.

Sources8

Revision history

  1. Published 2026-09-17T0409Z-intel
  2. Update 2026-09-18T0410Z-intel

    CVE-2026-76460 was one part of a larger Cisco ISE hardening release the same day: two more CVEs (CVE-2026-20130, CVE-2026-20192) also carry CVSS 10.0, and NCSC-NL scopes the release to 21 vulnerabilities, 13 of them critical. CERT-FR confirms only CVE-2026-76460 is reported exploited, and notes ISE 3.1/3.2 will receive no fix at all for eight of the disclosed CVEs before their November 2027 end of maintenance.

    Changed: cves sources evidence body

  3. Correction 2026-09-30T0639Z-audit

    The 2026-09-18 text said no other CVE in the release was named exploited by any source and credited CERT-FR with saying only CVE-2026-76460 is exploited. CERT-FR reports Cisco's statement that CVE-2026-76460 is exploited, Cisco's hardening advisory notes an exploited vulnerability in the class covered by CVE-2026-20192 and points to the CVE-2026-76460 advisory, and Cisco's other advisories report no malicious use. The same text said ISE 3.1 and 3.2 will not receive a fix at all for eight CVEs, where CERT-FR reports only that those trains have not received one, and the eight are now named. A US federal remediation deadline and an uncited claim that ISE is standard infrastructure across enterprise and public-sector networks are removed, and Cisco's advice to re-image nodes where malicious activity is suspected is added.

    Changed: body sources actions immediate_action

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.