Cisco ISE, Email Security and Backup Threats for Small Businesses

This week, active exploitation affects products trusted to control network access, filter malicious email, and protect server backups.

September 14, 2026 • Under 10 minute read • Gabriel Guastella

The 60-Second Version

If you manage Cisco Secure Email Gateway or Cisco ISE, start there. Both have actively exploited vulnerabilities that can lead to serious administrative access. Do not stop after installing the update. Review the environment for evidence that someone arrived before the patch did.

Next, identify affected Acronis hosting integrations, begin testing iOS 27 and iPadOS 27 on managed devices, and take a hard look at whether your monitoring could spot an attacker using legitimate credentials.

The basic rule this week: When the security tool becomes the target, treat it as a possible security incident, not another routine patch ticket.

Every week, I sort through security advisories and try to separate the things that actually deserve attention from the things that only exist to make vulnerability dashboards glow red. This week, unfortunately, the answer is pretty clear.

Three tools organizations trust to protect something important are themselves under attack: Cisco Secure Email Gateway, Cisco ISE, and several Acronis backup integrations. That is not a fun combination. We are talking about email filtering, network access control, and backups. Basically, the locks, the security desk, and the spare key under the mat.

We also have a sizable Apple security update, some genuinely useful guidance from CISA on cyber decoys, and a spyware campaign that shows how far attackers will go to make a malicious message feel personal.

Here is what actually matters.

01

Cisco Secure Email Gateway can be compromised by an email

Cisco disclosed CVE-2026-76461, a critical SQL injection vulnerability affecting physical and virtual Cisco Secure Email Gateway appliances.

The uncomfortable part is how the attack reaches the appliance. An attacker can send a specially crafted email through the gateway and exploit the system’s email-parsing logic. No employee needs to open the message or click a link.

If successful, the attacker may be able to run commands with root privileges. Cisco has confirmed active exploitation and says there is no workaround.

Why this matters

An email gateway is supposed to inspect hostile messages before they reach the rest of the business. It has to accept email from the internet to do that job, which also gives attackers a direct path to the vulnerable component.

Root access makes this more than a patching problem. An attacker with that level of control may be able to alter logs, remove evidence, steal credentials, access cryptographic material, or use the appliance to reach something else.

So yes, the machine responsible for inspecting suspicious email may now need to be inspected itself.

What IT teams should do

  • Upgrade to the appropriate fixed release:

    • Version 15.5 and earlier: 15.5.5-014
    • Version 16.0: 16.0.4-302
    • Version 16.5: 16.5.0-780

    Cisco recommends that customers running versions older than 16.5 move to 16.5.0-780.

    After updating:

    • Review mail_logs for suspicious SQL statements.
    • Check every member of an appliance cluster.
    • Compare the appliance logs with firewall, DNS, proxy, and network logs stored somewhere else.
    • Look for unusual uploads, downloads, outbound connections, or configuration changes.
    • Preserve forensic information before replacing or rebuilding a virtual appliance.
    • Rotate credentials, certificates, cryptographic material, and cluster SSH keys if compromise is possible.

    Cisco has already updated its managed Secure Email Cloud environment. Organizations running their own appliances need to handle the upgrade and investigation directly.

    Read the Cisco Secure Email Gateway advisory?

02

Cisco ISE authentication bypass is already being exploited

The second Cisco problem is CVE-2026-76460, a maximum-severity vulnerability affecting Cisco Identity Services Engine and ISE Passive Identity Connector.

An unauthenticated attacker can send a crafted request to a vulnerable API endpoint and bypass the web management interface. Cisco warns that successful exploitation may ultimately provide root command execution.

The vulnerability affects ISE and ISE-PIC regardless of how they are configured, and Cisco has confirmed active exploitation.

Why this matters

Cisco ISE helps decide which users and devices can join the network and what they are allowed to access afterward.

Compromising ISE is not like compromising an ordinary workstation. It potentially gives the attacker control over a system responsible for enforcing network trust.

It is the digital equivalent of walking past the security guard and taking over the desk that prints the access badges.

What IT teams should do

Install the appropriate fixed release:

  • ISE 3.1: 3.1 Patch 12
  • ISE 3.2: 3.2 Patch 11
  • ISE 3.3: 3.3 Patch 12
  • ISE 3.4: 3.4 Patch 7
  • ISE 3.5: 3.5 Patch 4

ISE 3.0 has reached the end of software maintenance and should be migrated to a supported release.

Once the update is handled:

  • Restrict management and control-plane access with infrastructure ACLs.
  • Review ise-kong/access.log and archived API gateway logs on every node.
  • Search for suspicious usernames, including Cisco’s published dummyuser example.
  • Review recent administrator, identity, policy, and network-access changes.
  • Compare ISE activity with firewall and network logs stored outside the appliance.
  • Re-image affected nodes and restore from a trusted configuration backup if malicious activity is found.

Cisco does provide an ACL-based mitigation to limit remote exploitation, but that is temporary protection. It is not a substitute for installing the fixed release.

CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on September 16.

Read the Cisco ISE security advisory?

03

Acronis backup integrations are being targeted

The next problem affects several Linux-based Acronis backup integrations.

CVE-2026-87886 is a local privilege-escalation vulnerability caused by insecure file permissions. CISA added it to the Known Exploited Vulnerabilities catalog after evidence of targeted exploitation.

Affected products include older builds of:

  • Acronis Backup plugin for cPanel and WHM
  • Acronis Backup extension for Plesk
  • Acronis Backup plugin for DirectAdmin

Why this matters

This vulnerability requires an attacker to have some level of local access first, so it is not the same kind of direct remote attack as the Cisco vulnerabilities.

That does not make it harmless.

Hosting servers often contain multiple websites, databases, mailboxes, administrative tools, and customer accounts. Turning limited access into elevated privileges could give an attacker control over far more than the account they originally compromised.

The backup integration also sits close to the systems and recovery data you would depend on during an incident.

Backups are supposed to be the escape hatch. They should not become the attacker’s ladder.

Confirm that each integration meets or exceeds these fixed builds:

  • cPanel and WHM plugin: 1.9.3.1021
  • Plesk extension: 1.8.11.638
  • DirectAdmin plugin: 1.2.3.238

Then check the surrounding server:

  • Review privileged file ownership and permissions.
  • Investigate unexpected root-level processes or commands.
  • Look for unfamiliar accounts, SSH keys, scheduled jobs, and startup persistence.
  • Review backup destinations, exclusions, retention settings, and deleted restore points.
  • Confirm that clean backups exist outside the affected server.
  • Rotate credentials available to the hosting control panel or backup integration if compromise cannot be ruled out.

Do not let a successful backup-job notification be the only proof that recovery data is safe. Test an actual restore.

Read the Acronis security advisory?

04

iOS 27 is also a security update

Apple released iOS 27 and iPadOS 27 on September 14 with a long list of security fixes.

The update addresses vulnerabilities involving Bluetooth code execution, Apple Account authentication, kernel permissions, Keychain credentials, protected system files, network restrictions, and access to sensitive data.

Apple has not identified these particular issues as actively exploited, but the security content is substantial enough that businesses should not treat this as a cosmetic feature upgrade.

Why this matters

Major mobile operating-system releases are often postponed because people expect broken applications, changed interfaces, or the inevitable employee who discovers every new button before IT has finished reading the release notes.

Some caution is reasonable. Leaving business devices behind indefinitely is not.

Phones and tablets regularly contain business email, Microsoft 365 sessions, MFA applications, cloud files, saved credentials, customer conversations, and VPN access. They are business endpoints, even if employees occasionally use them to watch videos in the parking lot.

What IT teams should do

  • Test iOS 27 and iPadOS 27 with your critical business applications.
  • Confirm compatibility with Microsoft 365, MFA, VPN, RMM, MDM, and line-of-business tools.
  • Begin a phased rollout after initial testing.
  • Set a real deployment deadline.
  • Inventory devices that cannot run the new version.
  • Create a replacement or risk-acceptance plan for unsupported hardware.
  • Verify update and compliance status through MDM reporting.

“Available to install” is not the same thing as installed.

Review Apple’s iOS 27 and iPadOS 27 security content?

05

CISA published practical guidance on cyber decoys

Not everything this week is another emergency patch.

CISA published new guidance on using cyber decoys to detect attackers who have already entered an environment.

These decoys can include fake credentials, documents, accounts, file shares, systems, or other resources designed to look valuable to an intruder. Because they serve no legitimate business purpose, interacting with one can generate a very high-confidence security alert.

Why this matters

Attackers increasingly use legitimate credentials and built-in administrative tools. That activity can be difficult to separate from normal IT work, particularly in an environment with limited monitoring.

A well-placed decoy changes the question.

Instead of asking, “Does this PowerShell command look suspicious enough?” you can ask, “Why did someone just use the fake administrator credential hidden where no employee should ever need it?”

That is usually a much shorter meeting.

What IT teams should do

Start small:

  • Create a limited number of low-risk honeytokens or decoy documents.
  • Place them where an attacker performing network discovery might find them.
  • Make sure fake credentials cannot access real systems.
  • Route alerts to a platform that someone actively monitors.
  • Document who owns each decoy and what should happen if it is triggered.
  • Test the entire alert path.
  • Review decoys periodically so they do not become forgotten clutter.

Cyber decoys do not replace EDR, MFA, segmentation, patching, or centralized logging. They add another way to catch an attacker whose behavior might otherwise look legitimate.

Read CISA’s cyber-decoy guidance?

06

CHOSEN BRICK is a lesson in deeply personal phishing

The UK National Cyber Security Centre, FBI, and Netherlands’ AIVD released a joint advisory about CHOSEN BRICK, Windows spyware connected to Iranian state actors.

The observed campaign targets dissidents, activists, and journalists rather than ordinary small businesses. Still, the delivery method is worth understanding.

Attackers impersonate trusted contacts through WhatsApp and Telegram, spend time building rapport, and send files tailored to the victim’s interests or circumstances.

In one case, the attackers used fabricated MRI results.

The malware can capture screens, access the microphone, and collect emails, contacts, and social-media messages. It also establishes persistence so it can survive a reboot.

Why this matters

Phishing is no longer confined to email.

Employees communicate with customers, vendors, coworkers, and executives through text messages, LinkedIn, WhatsApp, Telegram, and personal accounts. Those conversations often feel more trustworthy because they are informal.

Attackers understand that. A familiar name, the correct profile photo, and one believable personal detail can carry more weight than a perfectly written email.

What IT teams should do

  • Include messaging platforms and social media in security-awareness training.
  • Verify unexpected files through a second communication method.
  • Do not trust a request solely because it came from a known account.
  • Be especially cautious with password-protected archives and unexpected documents.
  • Use EDR to monitor suspicious Run-key persistence and unusual child processes.
  • Escalate highly personalized messages involving executives or sensitive employees.
  • Preserve the device and begin incident response if spyware execution is suspected.

The lesson for most businesses is not that Iran is coming after the accounting department with fake medical records. It is that modern phishing can be patient, personal, and disturbingly well researched.

Read the NCSC CHOSEN BRICK advisory?

Your order of operations

This week’s priority queue

If you are looking at the full list and wondering where to begin, use this order:

  1. Cisco Secure Email Gateway: Patch it and investigate for prior exploitation.
  2. Cisco ISE and ISE-PIC: Install the fixed release and review every node.
  3. Acronis hosting integrations: Find affected installations, update them, and validate the backups.
  4. ScreenConnect and N-central: Confirm that last week’s emergency remediation actually reached the required servers, clients, and technician devices.
  5. Apple devices: Begin compatibility testing and phased deployment of iOS 27 and iPadOS 27.
  6. Monitoring: Evaluate whether a small cyber-decoy pilot could improve detection.
  7. User awareness: Expand phishing training beyond the traditional inbox.

This is what I want from a weekly security brief: not forty red banners and a list of CVE numbers, but a useful order of operations.

The common thread this week is trust.

We trust an email gateway to inspect dangerous messages. We trust ISE to decide who belongs on the network. We trust backup software to protect our recovery options. We trust a familiar name and photo when a message appears on our phone.

Attackers know which systems and people we trust. Our job is to keep verifying that the trust is deserved.

If you are unsure whether your business uses any of these products, ask your IT provider directly. A useful answer should explain what is deployed, whether it is affected, what was updated, whether signs of compromise were reviewed, and how the completed work was verified.

The Watchdog takeaway

Management tools deserve more protection, not less.

If a platform can reach every endpoint, server, firewall, or customer environment you manage, it belongs at the front of the patching, monitoring, and incident-response queue.