Cybersecurity

Cisco's network gatekeeper had a perfect 10 hole in it

Key takeaways

  • Patch Cisco ISE immediately, no workaround exists
  • Check whether your ISE admin interface is exposed to the internet
  • CISA set a 19 September 2026 deadline for federal agencies

Cisco has confirmed that a maximum severity flaw in Identity Services Engine (ISE), the system many large networks use to decide who gets in, was being exploited before a patch existed. On 16 September 2026, the company disclosed CVE-2026-76460, which scores a full 10.0 on the CVSS scale. An attacker needs no password, token or foothold to use it.

According to Cisco's advisory and The Register's coverage, successful exploitation gives the attacker command execution with root privileges. On a device whose whole job is judging who is trustworthy, that is about as bad as it gets.

What is Cisco ISE and why does it matter?

Cisco Identity Services Engine is a network access control (NAC) platform. When you plug in a laptop, join corporate Wi-Fi or connect to a VPN, ISE is usually the system quietly checking your identity and your device before it lets you through. It also applies policy, such as which staff can reach which parts of the network.

Because of that role, ISE deployments tend to sit deep inside corporate networks, often trusted by everything around them. A bug here is far more dangerous than the same bug in a random internet-facing app.

What is CVE-2026-76460?

The flaw sits in an API endpoint with insufficient authentication control. In plain terms, one of the interfaces ISE exposes does not properly check who is calling it. Send the right request and you bypass login completely.

CVSS, the Common Vulnerability Scoring System, rates severity from 0 to 10. A 10.0 is the ceiling, and it is reserved for flaws that can be exploited remotely, need no privileges and no user interaction, and give an attacker full control. Very few bugs earn it.

What can an attacker do with it?

Cisco says exploitation hands over command execution as root, the most privileged account on the system. An attacker in that position can change policy, read or alter configuration and potentially decide which other devices and users are allowed onto the network behind them.

That is the real danger. An attacker who skips the front door on your identity system does not just get one account. They potentially get the keys to deciding who else gets to walk in.

Is it being exploited?

Yes. Cisco confirmed active exploitation in the wild before the patch was even public. That makes CVE-2026-76460 a zero-day, a flaw attackers are using before the vendor has shipped a fix.

CISA, the US Cybersecurity and Infrastructure Security Agency, moved quickly. It added the flaw to its Known Exploited Vulnerabilities (KEV) catalogue with a deadline of 19 September 2026 for federal agencies to patch, only three days after Cisco's disclosure. Our guide on how to check the CISA KEV catalogue explains how to watch that list yourself.

That short window fits a wider trend. CISA has been tightening deadlines, as we covered when CISA cut the patch window to three days, and the KEV catalogue has been filling quickly, with ten exploited flaws in seven days added recently.

Why do authentication bypasses in API endpoints keep happening?

Modern appliances expose management functions through web APIs, and every endpoint has to enforce its own login check. If one endpoint is missed, or a check can be skipped by sending a request in an unexpected form, the rest of the product's careful access control counts for nothing. Security teams call this broken authentication, and it is one of the most common causes of critical flaws in network management software.

For defenders, the lesson is that a patch is only half the job. Reducing who can reach the management plane in the first place limits the damage when the next endpoint is missed.

Is there a workaround?

No. There is no configuration tweak and no firewall rule that neutralises the flaw. The only fix is the patch itself.

Cisco disclosed nine vulnerabilities in ISE that day as part of a broader hardening release, so the advisory (cisco-sa-hardening-ise-XU5EwX5T) is worth reading in full. It lists the fixed software versions for each release train.

Quick reference

DetailWhat we know
ProductCisco Identity Services Engine (ISE)
IdentifierCVE-2026-76460
Severity10.0 on the CVSS scale, the maximum
WeaknessInsufficient authentication control in an API endpoint
ImpactLogin bypass, then command execution with root privileges
Exploited in the wildYes, before the patch was public
Disclosed16 September 2026, alongside nine ISE vulnerabilities
CISA deadline19 September 2026 for federal agencies
WorkaroundNone, patch only

What should you do now?

If you run ISE, or manage a network where someone else does, the advice is blunt: patch now and do not wait for a maintenance window. Cisco's advisory has the fixed versions.

Check that your ISE admin interface is not exposed to the wider internet while you are at it. That is the most obvious way a flaw like this gets exploited at scale. Management interfaces belong on a dedicated, restricted network, reachable only from a small set of admin machines.

Then look backwards. Because attackers were using the bug before the patch landed, patching alone does not tell you whether someone is already inside. If your organisation has any process for checking whether attackers got in first, such as reviewing ISE logs, admin account changes and unexpected policy edits, this is the week to run it, not skip it.

What does the three-day deadline tell us?

A deadline of 19 September 2026 for a flaw disclosed on 16 September 2026 shows how seriously CISA treated it. Federal agencies are bound by these dates, but private organisations tend to follow them as an informal benchmark. If CISA wants a flaw closed within days, any business running ISE should assume attackers are already scanning for it.

Is this a pattern for Cisco?

It is the second time this year Cisco's network access control gear has made headlines for the wrong reasons, and the company's other products have had a rough run too. We have covered an auth bypass in Cisco Catalyst SD-WAN, a flaw that hands attackers admin on SD-WAN Manager and an attack on Cisco's email gateway.

It is not only Cisco. GitLab, for one, scored a perfect 10 on the vulnerability scale and attackers noticed quickly there too.

There is a bigger design question here as well. Enterprise security teams have spent the last few years pushing "zero trust" architectures that lean heavily on identity infrastructure like ISE. When the system enforcing zero trust turns out to have a hole allowing zero authentication, it is a reminder that centralising trust in one system also centralises risk.

Read more: Cisco Security Advisory: ISE Hardening Release September 2026, The Register: Cisco drops another exploited zero-day, this time a perfect 10

More from Future Technology HQ