
In October 2026, flaws in devices that sit at the edge of a network, such as VPNs, firewalls, email gateways and remote-support tools, have been exploited one after another. In the CISA KEV (the catalog of Known Exploited Vulnerabilities), the version published at 19:30 UTC on October 23 has 26 vulnerabilities with an added date between October 1 and October 23 (I counted these from the added dates in that data). They include products from Ivanti, Citrix, Palo Alto Networks, Cisco, Fortinet, BeyondTrust, Arista and, in Japan, SiteGuard.
This article is for executives and the people who run IT. Built around vendor advisories and CISA’s statements, it covers which devices are affected, what to do before updating, and why updating alone is not enough. Sources are cited next to each statement. The information is current as of October 25, 2026 JST.
This is a summary based on CISA’s KEV descriptions and each vendor’s advisory. “KEV added” is the date the entry was added to the KEV. Always confirm the fixed version numbers in each vendor’s advisory.
| Product | CVE | KEV added | What it is | Conditions and status |
|---|---|---|---|---|
| Citrix NetScaler ADC / Gateway | CVE-2026-88771, 88772, 88779 | Sept 27 (88771, 88772), Oct 4 (88779) | 88771: improper input validation lets an unauthenticated attacker run commands. 88772: an out-of-bounds memory operation, leading to remote code execution or denial of service. 88779: denial of service | CISA says they are being exploited worldwide. In SAML configurations, 88779 can force a reboot so that code injected through 88771 runs |
| Ivanti Connect Secure | CVE-2026-104935 | Oct 13 | Authentication bypass that lets an unauthenticated attacker run commands | Affects 22.8R2.4 and earlier, 25.1.2.2 and earlier, and 25.1.1.1 and earlier (BleepingComputer, citing Ivanti). For fixed versions, see Ivanti’s advisory |
| Palo Alto Networks PAN-OS | CVE-2026-0322 | Oct 14 | Remote code execution in the management interface, with root privileges on the firewall | The attacker must be authenticated and have network access to the management interface. CVSS 4.0 8.6. The vendor reports “very limited exploitation” and says there is no workaround (Palo Alto Networks) |
| Cisco Secure Email Gateway | CVE-2026-76519 | Oct 14 | An unauthenticated remote attacker can write arbitrary files to the OS with a crafted email attachment. CVSS 9.8 | When File Reputation is enabled and Content Scanner Tools is earlier than 25.3.0.5525. Cisco is aware of exploitation and there is no workaround (Cisco). Fixes: 15.5.5-014, 16.5.0-780, or Content Scanner Tools 25.3.0.5525 or later |
| Fortinet FortiMail | CVE-2026-104286 | Oct 1 | An unauthenticated attacker can write arbitrary files with crafted HTTP/HTTPS requests | Affects 8.0.0 to 8.0.1, 7.6.0 to 7.6.6, 7.4.0 to 7.4.8 and 7.2.0 to 7.2.9. Fixed in 8.0.2, 7.6.7 and 7.4.9 or later. For 7.2, move to 7.4 or later. Workarounds include disabling the IBE service. FortiMail Cloud was fixed on October 5 (Fortinet) |
| Fortinet FortiOS and others | CVE-2025-61624 | Oct 16 | An authenticated attacker with admin rights can write or delete arbitrary files through specific CLI commands | See Fortinet’s advisory |
| BeyondTrust Remote Support | CVE-2026-102764 | Oct 16 | Authentication bypass (spoofing) that allows file operations on the appliance. CVSS v4 9.3 | Affects 26.2.3 and earlier. Fix: BT26-05-RS. SaaS was patched on October 9. According to Rapid7, BeyondTrust dates two compromises to August 29 |
| Arista VeloCloud Orchestrator (on-prem) | CVE-2026-114625 | Oct 23 | SQL injection that affects the orchestrator host | Affects 5.2.x before 5.2.3.18, 6.1.x before 6.1.3.10 and 6.4.x before 6.4.2.12. Arista is aware of exploitation (Arista). The KEV remediation due date is October 26 |
| SiteGuard Server Edition (EG Secure Solutions) | CVE-2026-106931 | Oct 20 | OS command injection in the statistics feature, allowing arbitrary commands with root or SYSTEM privileges. CVSS v4.0 8.5 | Affects the Apache, Nginx and IIS editions before Ver8.00 Update5, among others. Exploitation is confirmed. It was published on October 14, and customers with a support contract had been notified individually on September 29 (EG Secure Solutions) |
On Ivanti, BleepingComputer reports that Volexity said an actor it tracks as UTA0576 had been chaining this flaw with two others since October 3 (Defused says it saw the first signs on October 1). The actor reportedly dropped no malware and no web shell, re-exploited the device for each command, and tampered with logs, so Ivanti’s Integrity Checker Tool (ICT) did not detect it. One of the chained flaws (a privilege escalation) was unpatched at the time of the report. I could not retrieve Ivanti’s own page, so this part rests on the press report.
On BeyondTrust, Rapid7 says BeyondTrust dates two compromises to August 29, before its October 15 disclosure. Mandiant ties the activity to a suspected PRC-nexus espionage actor.
The same kind of intrusion has happened in Japan. On September 11, the Digital Agency announced that unauthorized access to the Government Solution Service (GSS) may have leaked the personal information of about 246,000 people.
From detection to announcement was 78 days (June 25 to September 11, my own calculation). The Digital Agency lists a review of how it manages vulnerabilities and better ways of connecting externally among its prevention steps.
Separately, in the National Police Agency’s first-half 2026 summary, ransomware reports numbered 123, the most for any half-year since statistics began in 2020 (@IT, a press report; I have not checked the NPA original).
These three points are my own observations.
In its Citrix alert, CISA lays out these steps. Before updating, check for signs of compromise, and if compromise is suspected, preserve forensic evidence before updating, because an update can reduce what is available to investigate. Then restore a known-good backup from before any compromise and rotate every stored secret (account passwords, key-encryption keys and SSL certificates). Forward logs to a SIEM outside the device, because logs on the device can rotate quickly.
The directive for US federal agencies, BOD 26-04 (June 10, 2026), likewise requires that, for items marked for forensic triage, remediation and a check for compromise both be completed within three days. The directive covers federal agencies, but the thinking is useful for private companies too.
If you need help taking stock of your edge devices, updating them or checking for compromise, get in touch below.
We are currently taking free consultations on security. Questions like "Is our site safe?" or "Where should we start checking?" are welcome.
