CVE-2026-76446: Cisco ISE External Entity Injection Vulnerability

P2 — REVIEWCISCO PSIRTADVISORY SIR: MEDIUMPUBLIC ANNOUNCEMENT: YESMALICIOUS USE: NOT REPORTED

Quick Answer

CVE-2026-76446 permits authenticated XML external-entity requests to read files through an ISE or ISE-PIC API. Access is limited by the underlying process's file permissions, and Cisco's vector specifies High privileges. Apply the CVE-specific fix without treating the flaw as unauthenticated access to every file.

Fix Or Immediate Action

What to do now: Confirm the affected product, release, and configuration. Cisco provides no workaround; reduce exposure where operationally feasible. Upgrade to the CVE-specific First Fixed release in Cisco's advisory table.

Open the live Cisco advisory

Last verified: 2026-09-17 UTC from Cisco's advisory and CSAF record. Recheck both the affected-products and fixed-software sections before a production change.

Context

Scope And Impact In Plain Language

Who should check: Operators of Cisco ISE and ISE-PIC with the affected API in scope.

When this applies: Cisco lists vulnerable ISE and ISE-PIC releases regardless of configuration. The attack is authenticated; the published vector specifies High privileges.

What could happen: An authenticated remote attacker may submit XML external-entity references through an API and read specific operating-system files that the underlying process is permitted to access. That permission boundary matters: the description does not establish access to every file on the device.

Not sure? Find the exact product, platform, and version in the management interface or CLI, then compare them with this CVE's affected-products section in Cisco's live advisory.

Status At A Glance

Product scopeCisco Identity Services Engine (ISE)
CVECVE-2026-76446
TechGeeks response tierP2 — review and schedule
PublicationNew final Cisco advisory
First published2026-09-16T16:00:00+00:00
Last updated2026-09-16T16:00:00+00:00
Cisco advisory SIRMedium
CVE-specific Cisco SIRMedium
CVSS base score / severity4.9 — Medium
CVSS vectorCVSS v3.1 — CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
CISA KEV at last checkNo — this is separate from Cisco severity and is not proof of no exploitation.
Cisco exploitation statementThe Cisco PSIRT is aware that a public announcement is available for the vulnerabilities that are described in this advisory. The Cisco PSIRT is not aware of any malicious use of the vulnerabilities that are described in this advisory.

What Happened

An API in ISE and ISE-PIC does not properly restrict XML external-entity references. An authenticated attacker can send a crafted request that reads specific operating-system files accessible to the API's underlying process. Cisco tracks the defect as CSCwu73808. The process-permission boundary remains part of the documented impact.

Affected Scope

At publication, this vulnerability affected Cisco ISE and Cisco ISE-PIC regardless of device configuration.

Match the exact hardware or virtual platform, installed train, patch level, enabled service, role, and management or data-plane exposure. A Cisco product-family name alone does not establish applicability.

Steps

What To Do Now

  1. Confirm. Inventory Cisco Identity Services Engine (ISE) and record platform, exact release, patch level, enabled feature, role, and exposure.
  2. Preserve. Save UTC context plus off-device authentication, management, firewall, network, endpoint, and SIEM evidence before logs rotate or a disruptive change removes context.
  3. Scope. Compare each asset with the live Cisco advisory, including configuration prerequisites and exclusions.
  4. Reduce exposure. Cisco documents no workaround for this CVE. Use only supported exposure controls while preparing the permanent fix.
  5. Remediate. Confirm the affected product, release, and configuration. Cisco provides no workaround; reduce exposure where operationally feasible. Upgrade to the CVE-specific First Fixed release in Cisco's advisory table.
  6. Validate. Confirm the resulting version, service health, logging, expected access, an expected denial, failover or cluster state, and representative dependent workflows.
  7. Escalate. If evidence or exposure creates concern, open incident response and Cisco TAC recovery work rather than treating patch completion as proof of trust.

Fixed Releases And Mitigation

Permanent Fix

Cisco method: Use the live advisory's CVE-specific First Fixed Release table.

No compact per-CVE fixed-release table is reproduced here because Cisco may use different First Fixed values by CVE and software train. Use this CVE's live advisory table or Cisco Software Checker; do not infer a fixed release from a combined hardening baseline or another Cisco notice.

Workaround Or Temporary Mitigation

No vendor workaround is documented for CVE-2026-76446. Use supported exposure controls only as temporary risk reduction while preparing the permanent software fix.

Important boundary: A workaround, ACL, exposure reduction, or service restriction can reduce risk while the update is prepared, but it does not patch the vulnerable code, prove every attack path is closed, or erase an earlier compromise.

Investigation And Recovery

Review management authentication, account and privilege changes, API and web requests, configuration changes, crashes or restarts, resource pressure, and relevant external network telemetry for the vulnerable period. Preserve original evidence and follow Cisco TAC or incident-response guidance for containment, credential rotation, trusted rebuild, or service restoration when findings warrant it.

Notes

Exploitation Evidence

Cisco's exact status at the last check: The Cisco PSIRT is aware that a public announcement is available for the vulnerabilities that are described in this advisory. The Cisco PSIRT is not aware of any malicious use of the vulnerabilities that are described in this advisory.

This CVE was not present in the TechGeeks CISA KEV snapshot at the last check. Cisco's 'not aware' statement and absence from KEV are time-bounded evidence, not claims that exploitation is impossible or has never happened. Severity and exploitation status remain separate signals.

Validation And Boundaries

This notice is documentation-backed. TechGeeks did not reproduce the exploit or independently test every fixed build. It does not prove that all members of the product family are affected, that the activity is widespread, that a clean indicator search excludes compromise, or that an update restored trust. Cisco's live advisory controls affected and fixed release information.

Related TechGeeks Resources

References

Wrap-Up

Record whether CVE-2026-76446 applies. If it does, assign an owner and deadline appropriate to the Medium Cisco advisory SIR, preserve the evidence, complete Cisco's remediation, and document the validated result.

Correction policy: A material Cisco revision to scope, severity, exploitation status, workarounds, fixed software, or recovery guidance triggers an update and a new verification date.