October 25, 2026

VPNs, Email Gateways and Remote-Support Tools: The Edge Devices Exploited This Month, and What to Check Now

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.

Key points

  • At least nine edge products were confirmed exploited this month (see the table below). All of them are in the CISA KEV.
  • Ivanti, BeyondTrust and Citrix were exploited before fixes were available. If an attacker got in before you updated, updating does not remove the compromise.
  • CISA asks for a check for compromise (forensic triage) and for evidence to be preserved before updating, because updating can destroy evidence.
  • The Digital Agency incident, in which about 246,000 people’s information may have leaked, also started with a VPN device vulnerability.
  • The first thing to do now is list your edge devices and check whether any of the products confirmed exploited are among them.

Edge devices confirmed exploited this month

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.

A case in Japan: the Digital Agency’s Government Solution Service

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.

  • June 25: a large number of file accesses through a maintenance and operations account was detected
  • July 9: it was found that a third party had broken in through a VPN device vulnerability. The same day, the account was suspended and the compromised device’s external communications were cut
  • September 11: announced publicly
  • What may have leaked: about 246,000 people (about 189,000 staff of government agencies and related public officials, and about 57,000 business operators and individuals). Names about 236,000, email addresses about 231,000, phone numbers about 94,000, street addresses about 1,000 (records may overlap). My Number, bank account information and pension numbers were not included
  • Secondary harm: none confirmed

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).

Why updating alone is not enough

These three points are my own observations.

  • Edge devices face the internet directly, so attackers find them first. In this October’s examples, Ivanti and BeyondTrust were exploited before fixes existed.
  • It is hard to run endpoint detection software on edge devices, and the logs inside them are sparse and overwritten quickly. A break-in is easy to miss.
  • An update closes the vulnerability inside the device, but it does not remove a foothold that was already planted. Rapid7 also says persistence can remain after patching.

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.

What to check now

Today

  1. List your edge devices: VPNs, firewalls, email gateways, load balancers, remote-support tools, SD-WAN management systems and backup consoles, anything reachable from the internet. CISA defines edge devices as devices on the network boundary that are reachable from the public internet (BOD 26-02)
  2. For each device, write down the product and version, and check whether any product in the table above is on the list
  3. If one is, preserve logs and diagnostic information before updating. For example, SiteGuard asks you to download and keep the “diagnostic information” from the admin console before updating. Arista asks you to preserve logs and file timestamps if compromise is suspected

This week

  1. Update. Confirm the fixed version numbers in each vendor’s advisory
  2. After updating, check for compromise. For Citrix, CISA describes running the IOCs provided in NetScaler Console to look for signs. As the report above shows, Ivanti’s integrity checker has been evaded, so do not rely on it alone
  3. Check that your admin interfaces are not exposed to the internet. Palo Alto says restricting management access to trusted internal addresses or a single jump box lowers the risk
  4. Forward the logs from your edge devices to a location outside the devices

This month

  1. Review the privileges and monitoring of maintenance accounts. In the Digital Agency incident, bulk file access through a maintenance and operations account is what triggered detection
  2. Bring your vendor-notification contacts up to date. SiteGuard notified customers with a support contract individually on September 29, about two weeks before the public announcement. If the contact on your contract or maintenance agreement is stale, that notice will not reach you
  3. Decide who updates edge devices and how often. Replace devices that are out of support

What I could not confirm

  • I could not retrieve the official advisories for Ivanti and BeyondTrust. The finer points for these two products rest on press reports and Rapid7’s analysis
  • I could not retrieve Citrix’s fixed version numbers, so I have not listed them
  • I could not check the National Police Agency original. The figure rests on a press report

If you need help taking stock of your edge devices, updating them or checking for compromise, get in touch below.

Free security consultations

We are currently taking free consultations on security. Questions like "Is our site safe?" or "Where should we start checking?" are welcome.

Super Sonic Design accepts consultations on website creation, application design, etc. Please feel free to contact us.
inquiring
他の最新記事
カテゴリー