# CISA KEV October 2026: known-exploited edge appliances

> Edge appliances CISA added to its Known Exploited Vulnerabilities catalog in October 2026, with due dates, fixed builds and what to collect before you patch.

Canonical: https://red.run.cloud/learn/cisa-kev-this-month-edge-appliance-tracker · By Timothy Lindblom · Published 2026-11-02 · Updated 2026-11-02

CISA added 36 vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog in October 2026, the last of them on 30 October. By our count 14 of them sit in edge appliances: firewalls, VPN gateways, email gateways and remote-support tools. Ivanti Connect Secure alone took three. If you run any, patch the exposed ones first, save the evidence the vendor asks for before the update, and rotate credentials afterwards.

| Fact | Detail | Source |
|---|---|---|
| Entries added in October 2026 | 36, from 1 to 30 October; none on 31 October | [KEV data file](https://raw.githubusercontent.com/cisagov/kev-data/main/known_exploited_vulnerabilities.csv) |
| Edge-appliance entries in October | 14, across 11 products | this page, from the same file |
| Federal due date | Usually 3 days after the date added. Fourteen days for two Plex entries and the Siemens entry (20 October), Brotli and an Adobe Commerce flaw (27 October), VMware ESX (28 October) and one Ivanti entry (30 October) | KEV data file |
| Who the due dates bind | US federal civilian agencies, under [BOD 26-04](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk) (10 June 2026, replaces BOD 22-01) | CISA |
| Ransomware use flag | "Unknown" on every October entry | KEV data file |
| Checked | 2 November 2026 | this page |

<div class="ln-stats"><div><b>36</b><span>KEV additions in October</span></div><div><b>14</b><span>of them edge appliances</span></div><div><b>3 days</b><span>typical federal due date</span></div></div>

This page is the monthly roll-up. Single incidents have their own pages, such as the [Adobe Commerce KEV entry](/learn/adobe-commerce-cve-2026-71362-kev-patch-check) and the [WordPress core entry](/learn/wordpress-core-cve-2026-87902-rce). The wider month is in the [month's other incidents](/learn/october-2026-security-meltdown-tracker).

## Which edge appliances did CISA add in October 2026?

Read the table by date added. "Federal due" is the date CISA gave agencies, not a deadline for you. Vendor notes are what the vendor's own page said at our check.

| Added | Product | CVE | Federal due | What the vendor or CISA says |
|---|---|---|---|---|
| 1 Oct | Fortinet FortiMail | CVE-2026-104286 | 4 Oct | CVSS 9.8, no login needed, confirmed exploited. [Fortinet](https://fortiguard.fortinet.com/psirt/FG-IR-26-175) |
| 4 Oct | Citrix NetScaler (SAML) | CVE-2026-88779 | 7 Oct | Third NetScaler CVE added in under two weeks. [CISA](https://www.cisa.gov/news-events/alerts/2026/09/27/critical-zero-day-vulnerabilities-exploited-citrix-netscaler-adc-gateway) |
| 13 Oct | Ivanti Connect Secure | CVE-2026-104935 | 16 Oct | Zero-day authentication bypass. [CISA](https://www.cisa.gov/news-events/alerts/2026/10/13/cisa-urges-patching-newly-exploited-vulnerability-ivanti-connect-secure) |
| 14 Oct | Palo Alto PAN-OS | CVE-2026-0322 | 17 Oct | CVSS 8.6, needs a login, "very limited exploitation". [Palo Alto](https://security.paloaltonetworks.com/CVE-2026-0322) |
| 14 Oct | Cisco Secure Email Gateway | CVE-2026-76519 | 17 Oct | CVSS 9.8, no workaround. [Cisco](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-esa-afw-zqYJkjxp) |
| 14 Oct | Ahsay AhsayCBS | CVE-2026-105133, CVE-2026-105134 | 17 Oct | Authentication and command injection flaws. [CISA](https://www.cisa.gov/news-events/alerts/2026/10/14/cisa-adds-four-known-exploited-vulnerabilities-catalog) |
| 16 Oct | BeyondTrust Remote Support | CVE-2026-102764 | 19 Oct | Self-hosted copies need the patch. [CISA](https://www.cisa.gov/news-events/alerts/2026/10/16/cisa-urges-patching-critical-vulnerability-beyondtrust-remote-support) |
| 16 Oct | Fortinet FortiOS, FortiPAM, FortiProxy, FortiSwitchManager | CVE-2025-61624 | 19 Oct | CVSS 6.0, "Known Exploited: Yes". [Fortinet](https://fortiguard.fortinet.com/psirt/FG-IR-26-122) |
| 20 Oct | EG Secure Solutions SiteGuard Server Edition | CVE-2026-106931 | 23 Oct | Command injection as root or SYSTEM. [JPCERT/CC](https://www.jpcert.or.jp/at/2026/at260032.html) |
| 23 Oct | Arista VeloCloud Orchestrator | CVE-2026-114625 | 26 Oct | SQL injection. [CISA](https://www.cisa.gov/news-events/alerts/2026/10/23/cisa-adds-one-known-exploited-vulnerability-catalog) |
| 29 Oct | Cisco Secure Firewall ASA and FTD | CVE-2026-76418 | 1 Nov | CVSS 8.6, no login needed, crashes the device through the Remote Access SSL VPN login when a tunnel group uses secondary authentication. Cisco confirms active exploitation. [Cisco](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asaftd-tunnel-dos-s6mgkb75) |
| 30 Oct | Ivanti Connect Secure | CVE-2026-111357 | 2 Nov | Privilege escalation to root, the last link of the CVE-2026-104935 chain. Patched 29 October. [Volexity](https://www.volexity.com/blog/2026/10/13/a-series-of-unauthenticated-events-chained-exploitation-of-ivanti-connect-secure-zero-days/) |
| 30 Oct | Ivanti Connect Secure | CVE-2026-118527 | 13 Nov | Predictable identifiers let a signed-in attacker write files to a known path; chains with the two above. [KEV data file](https://raw.githubusercontent.com/cisagov/kev-data/main/known_exploited_vulnerabilities.csv) |

The catalog also lists Collabora Online's built-in CODE server (CVE-2026-110447), added 23 October with a 26 October due date. It is a document server inside Nextcloud, not an edge appliance, so it stays out of the count. Collabora's [advisory](https://github.com/CollaboraOnline/online/security/advisories/GHSA-g3vx-3m76-fghh) puts the fix in built-in CODE server 26.4.303.

The last week of October also brought large entries outside the edge. CISA added both [PHP2Shell CVEs](/learn/php2shell) (CVE-2026-109618 and CVE-2026-109619) on 26 October, and on 28 October a Linux kernel flaw, CVE-2026-46300, that its entry says chains with them to plant PHP webshells and run commands as root. It added the Brotli decoder flaw CVE-2026-111497 and the July Adobe Commerce flaw CVE-2026-48356 on 27 October (the [Adobe Commerce KEV page](/learn/adobe-commerce-cve-2026-71362-kev-patch-check) covers both Adobe entries), VMware ESX CVE-2026-41709 on 28 October, and GitLab CVE-2026-97229 on 29 October, which [the GitLab upgrade guide](/learn/check-self-hosted-gitlab-version-and-upgrade) covers.

The list is not only new bugs. On 8 October CISA added five old flaws in ProFTPD, BIND, Apache Struts, ONLYOFFICE Docs and Strapi, the oldest from 2015. Old internet-facing services get retested by attackers, and an appliance that nobody updates carries them for years.

Most rows above have a page of their own: the [FortiMail file-write flaw](/learn/fortimail-cve-2026-104286-file-write), the [NetScaler SAML denial of service](/learn/netscaler-saml-dos-cve-2026-88779), [Ivanti's authentication bypass](/learn/ivanti-connect-secure-cve-2026-104935), the [PAN-OS management interface bug](/learn/pan-os-cve-2026-0322-management-rce), the [Cisco email gateway flaw](/learn/cisco-secure-email-gateway-cve-2026-76519), the [BeyondTrust remote-support zero-day](/learn/beyondtrust-remote-support-cve-2026-102764) and [SiteGuard's command injection](/learn/siteguard-waf-cve-2026-106931). The [other appliance guides](/learn/topics/appliances) cover the rest.

## What was still open from late September?

Several September entries have passed their federal due dates, and owners of the products still need to act. The two with their own pages are [F5 BIG-IP APM and its iRule](/learn/f5-big-ip-apm-cve-2026-94127) and the [NetScaler zero-day pair](/learn/netscaler-cve-2026-88771-88772-zero-days). We read the CISA entries for all of them. We read the vendor page only where linked.

| Added | Product | CVE | Note |
|---|---|---|---|
| 21 Sep | Zyxel GS1900 switches | CVE-2026-7273 | In the catalog; read the Zyxel advisory for your model |
| 22 Sep | F5 BIG-IP APM | CVE-2026-94127 | The [CISA alert](https://www.cisa.gov/news-events/alerts/2026/09/22/cisa-adds-four-known-exploited-vulnerabilities-catalog) says agencies must check for compromise before the patch |
| 22 Sep | Check Point (two products) | CVE-2026-93616, CVE-2026-85102 | Same alert. Read the Check Point advisory for fixed Jumbo Hotfix takes |
| 22 Sep | Arista VeloCloud Orchestrator | CVE-2026-93952 | Second Arista entry in a month |
| 25 Sep | MikroTik RouterOS | CVE-2026-67279 | Fixed in 7.24.2, 7.23.4 and 6.49.21 per [MikroTik](https://mikrotik.com/supportsec/september-2026-vulnerability/) |
| 27 Sep | Citrix NetScaler | CVE-2026-88771, CVE-2026-88772 | [CISA](https://www.cisa.gov/news-events/alerts/2026/09/27/critical-zero-day-vulnerabilities-exploited-citrix-netscaler-adc-gateway) says check for signs of compromise before patching |
| 30 Sep | Cisco Catalyst SD-WAN Manager | CVE-2026-76504 | CVSS 9.8, no workaround. [Cisco](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-webauth-xr8beuuU) |

MikroTik's page adds a detail that catches people: the first fixes for CVE-2026-67278 (forged TLS certificates and SSH keys) were incomplete. The complete fix needs 7.24.3 or 7.23.6.

## Does "in KEV" mean my device has been hacked?

No. KEV says CISA has evidence that someone exploited that flaw. It says nothing about your device. Two states exist before any other question: exposed or not exposed. A management interface that only your office network can reach is a different risk from one open to the internet, and Palo Alto's advisory says exactly that about CVE-2026-0322.

The due dates need one more caution. BOD 26-04 ties the clock to exposure, exploit automation and impact, and runs from 3 days to the next upgrade cycle. A three-day federal date is a statement about federal assets that face the internet. It is still a sensible clock for yours.

A low CVSS number does not move an entry down the list. The Fortinet CLI flaw scores 6.0 and needs a privileged account, and Fortinet still marks it exploited. Sort by exposure and by KEV status before you sort by score.

## Should I collect evidence before I patch?

For several of these, yes, and the vendor says so. The pattern is the same: save what the update might overwrite, patch the same day, restart, then rotate what the device could read.

<figure class="ln-figure">
<svg viewBox="0 0 720 150" role="img" xmlns="http://www.w3.org/2000/svg" font-family="Geist, sans-serif">
<title>Order of work for an exploited appliance: save evidence, patch, restart, rotate credentials</title>
<rect x="8" y="35" width="150" height="80" rx="14" fill="#FFF1EF" stroke="#EAD3CF"/>
<text x="83" y="70" text-anchor="middle" font-size="15" font-weight="600" fill="#1A0F0F">1. Save evidence</text>
<text x="83" y="92" text-anchor="middle" font-size="12" fill="#655553">logs, diagnostics</text>
<rect x="190" y="35" width="150" height="80" rx="14" fill="#FFFFFF" stroke="#EAD3CF"/>
<text x="265" y="70" text-anchor="middle" font-size="15" font-weight="600" fill="#1A0F0F">2. Patch</text>
<text x="265" y="92" text-anchor="middle" font-size="12" fill="#655553">fixed build or hotfix</text>
<rect x="372" y="35" width="150" height="80" rx="14" fill="#FFFFFF" stroke="#EAD3CF"/>
<text x="447" y="70" text-anchor="middle" font-size="15" font-weight="600" fill="#1A0F0F">3. Restart</text>
<text x="447" y="92" text-anchor="middle" font-size="12" fill="#655553">reboot, confirm build</text>
<rect x="554" y="35" width="150" height="80" rx="14" fill="#C70500"/>
<text x="629" y="70" text-anchor="middle" font-size="15" font-weight="600" fill="#FFFFFF">4. Rotate</text>
<text x="629" y="92" text-anchor="middle" font-size="12" fill="#FFF1EF">keys, passwords, certs</text>
<path d="M160 75 H188 M342 75 H370 M524 75 H552" stroke="#B00500" stroke-width="2.5" fill="none"/>
</svg>
<figcaption>Evidence first, because the update can remove it. Step 4 is separate from patching, since a patch removes nothing that was planted earlier.</figcaption>
</figure>

| Product | What to save before the update | Source |
|---|---|---|
| Cisco SD-WAN Manager | Run `request admin-tech` before upgrading. Look in `serviceproxy-access.log` for encoded requests to the `j_security_check` endpoint | [Cisco](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-webauth-xr8beuuU) |
| SiteGuard Server Edition | Take the diagnostic data in the web admin first, because updating may delete attack traces. Disable the statistics feature as an interim step | [JPCERT/CC](https://www.jpcert.or.jp/at/2026/at260032.html) |
| Ivanti Connect Secure | Network and memory forensics. The Integrity Checker Tool may not detect exploitation that ran in memory. Volexity adds that the attacker deleted debug and audit log entries, and lists requests to `welcome.cgi` with an `X-DSCGI-PATH` header naming `wu.cgi` as a marker | [CISA](https://www.cisa.gov/news-events/alerts/2026/10/13/cisa-urges-patching-newly-exploited-vulnerability-ivanti-connect-secure), [Volexity](https://www.volexity.com/blog/2026/10/13/a-series-of-unauthenticated-events-chained-exploitation-of-ivanti-connect-secure-zero-days/) |
| Cisco Secure Firewall ASA and FTD | No indicators published. Before upgrading, record which tunnel groups, including DefaultWEBVPNGroup, use `secondary-authentication-server-group`; removing it is Cisco's interim mitigation | [Cisco](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asaftd-tunnel-dos-s6mgkb75) |
| BeyondTrust Remote Support | Network and memory forensics; if compromised, isolate, rebuild and rotate all credentials | [CISA](https://www.cisa.gov/news-events/alerts/2026/10/16/cisa-urges-patching-critical-vulnerability-beyondtrust-remote-support) |
| Cisco Secure Email Gateway | If compromised, replace virtual appliances with new fixed ones, call Cisco TAC for physical ones, renew credentials and cryptographic material | [Cisco](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-esa-afw-zqYJkjxp) |
| AhsayCBS | Apply the hotfix and reboot the server afterwards | [Ahsay](https://www.ahsay.com/en/company/announcements/patch-cve-105133-105134) |

Ahsay's page names v10.3.4.45 as the fixed hotfix and says the earlier v10.3.4.0 patch did not fully fix the flaws. If you applied v10.3.4.0 and stopped there, check the build again.

For the full recovery sequence, use the [step-by-step response plan](/learn/website-incident-response-playbook) and the [guide to rotating secrets after a breach](/learn/rotate-secrets-after-a-breach-guide).

## Which of these does my hosted copy already cover?

Some vendors run the service for you. Some only run part of it. The wording matters, so ask for it in writing.

| Product | Hosted or cloud status | Self-hosted status |
|---|---|---|
| FortiMail | FortiMail Cloud updated on 5 October 2026, per [Fortinet](https://fortiguard.fortinet.com/psirt/FG-IR-26-175) | Upgrade to 8.0.2, 7.6.7 or 7.4.9 or later. Branch 7.2 must move to 7.4 or later |
| BeyondTrust Remote Support | Hosted service already patched, per [CISA](https://www.cisa.gov/news-events/alerts/2026/10/16/cisa-urges-patching-critical-vulnerability-beyondtrust-remote-support) | Versions 26.2.3 and earlier need patch BT26-05-RS (supported 24.3.1 and later) |
| Palo Alto PAN-OS | Cloud NGFW and Prisma Access are not affected, per [Palo Alto](https://security.paloaltonetworks.com/CVE-2026-0322) | PA-Series, VM-Series and Panorama need a fixed release for the branch |
| Cisco Secure Firewall ASA and FTD | Cloud-delivered Firewall, cdFMC and Secure Access are not affected, per [Cisco](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asaftd-tunnel-dos-s6mgkb75) | Upgrade, for example to ASA 9.22.3.200 or 9.24.1.27 and FTD 7.4.9 or 7.6.7; Cisco's Software Checker lists the rest |
| Everything else | Not stated on the pages we read | Assume it is yours until the vendor says otherwise |

If a managed-service provider runs your gateway or VPN, the question of who patches belongs on paper before the next entry lands. The page on [who owns patching duties](/learn/who-is-responsible-for-patching-my-website) covers the split.

### What to send your provider

> For **[our firewall, VPN gateway or email gateway]**, is it exposed to the internet, and is it listed in CISA KEV in October 2026? Please give the model, the software build before and after your change, the time it was restarted, whether you saved diagnostic data before updating, and the date you last rotated its admin credentials and certificates.

## Am I affected? A three-state self-test

<div class="ln-selftest">
<h3>Am I affected? Where you stand right now</h3>
<p>A scan from outside can see a login page or a version string on a device. It cannot see the build behind a hidden banner, a management interface limited to inside your network, or when the device was last restarted.</p>
<ol>
<li><span class="ln-state ln-state-detected">Detected</span> <strong>A device on your address space shows a product and a version below the fixed build in the vendor advisory.</strong> Treat it as exposed. Save the evidence the vendor lists, patch, restart, then review for compromise.</li>
<li><span class="ln-state ln-state-unknown">Unknown</span> <strong>The version is hidden, the product is run for you, or you do not know whether the management interface faces the internet.</strong> This is the common case. Ask whoever runs the device the question above.</li>
<li><span class="ln-state ln-state-confirmed">Confirmed by owner evidence</span> <strong>You hold the vendor's fixed build number on the device, a restart after it, and a record of what was saved or checked for compromise.</strong> The device is patched. Whether anything got in earlier is a separate question.</li>
</ol>
<p>No scan, ours included, moves you from "unknown" to "confirmed".</p>
</div>

## This week's checklist

- [ ] List every firewall, VPN gateway, email gateway, remote-support tool and backup server your business or your clients use. Include the ones a provider runs.
- [ ] Mark which of them have a management or login interface reachable from the internet.
- [ ] Match each product to the October table above. Open the vendor advisory linked in it for the fixed build.
- [ ] Save the evidence the vendor lists, then update. Record the build number and the restart time.
- [ ] Rotate the admin passwords, API keys, VPN pre-shared keys and certificates the device held.
- [ ] Move management interfaces behind a VPN or an allow-list. Palo Alto, MikroTik and Cisco all name this as a mitigation.
- [ ] Put a monthly KEV check in the calendar. The catalog is at cisa.gov, and the data file is public.

For the short version of this week's work across all products, use the [October 2026 security checklist](/learn/october-2026-security-checklist-this-week). To prove a fix landed and not just a package, follow [these steps for confirming a fix](/learn/how-to-verify-a-vulnerability-is-fixed).

## What can an outside scan show about these devices?

The free scan reads the stack your site serves and matches each version to known vulnerabilities. It also looks for panels, consoles and debug pages left online and for databases and services reachable from the internet. It is a lookup. It can say a version is affected. It cannot say whether your setup is exposed, whether the vendor backported a fix, or whether the device restarted.

That is the limit stated in [this note on scan limits](/learn/what-an-external-website-scan-cant-prove). Use the scan to find what is visible from outside and your vendor's evidence to settle the rest.

## What this page does not cover

We did not read vendor pages for Zyxel, F5, Check Point, Arista or the Collabora entry, and the Citrix bulletin would not open from our checker. Those rows rest on the CISA entries only. The next update of this page will add them when we can cite the vendor. PHP2Shell entered the catalog on 26 October, as listed above. GitLab CVE-2026-110264 and Plesk CVE-2026-68492 were still absent at our 2 November check.

## Questions people ask

### What is the CISA KEV catalog and do I have to follow it?

It is CISA's list of vulnerabilities with evidence of active exploitation. The due dates in it bind US federal civilian agencies under BOD 26-04 and nobody else. For everyone else it works as a priority list: an entry means someone is already using the flaw.

### Is a KEV entry already being used against sites like mine?

It means CISA has evidence of exploitation of that flaw somewhere. It does not say how many targets, which sectors or whether small sites are in scope. Treat any exposed product on the list as a patch-now item, and treat unexposed ones as a normal but quick job.

### Should I patch my firewall or VPN right away, or collect logs first?

Collect first when the vendor or CISA says so, then patch the same day. Cisco asks for admin-tech files before an SD-WAN Manager upgrade, and the SiteGuard vendor asks for diagnostic data because an update can remove attack traces. Do not delay the patch to analyse the data.

### My vendor says the cloud version is already patched. Do I need to do anything?

For the hosted service, usually not on the patching side. Fortinet says FortiMail Cloud was updated on 5 October and BeyondTrust says its hosted service was patched. Self-hosted copies, including ones you run in your own cloud account, are yours to patch. Ask the vendor in writing which one you have.

### Does a patched appliance mean it was not compromised?

No. A patch closes the hole and removes nothing planted before it. Ivanti's own integrity checker may miss exploitation that ran in memory, and Cisco tells owners of compromised email gateways to replace virtual appliances and renew credentials. Decide on compromise separately from patch state.

### Can a website scanner tell me whether my firewall or VPN is vulnerable?

Only partly. From outside it can see what a device exposes, such as a login page or a version string, and match a visible version to known vulnerabilities. It cannot see a hidden version, a backport, a management interface that is reachable only from inside, or whether the device was rebooted after patching.


## Sources

1. [CISA Known Exploited Vulnerabilities catalog](https://www.cisa.gov/known-exploited-vulnerabilities-catalog): The list this page tracks. Entries, dates added and due dates read on 2 November 2026.
2. [CISA KEV data file (cisagov/kev-data, CSV)](https://raw.githubusercontent.com/cisagov/kev-data/main/known_exploited_vulnerabilities.csv): Source of the counts and due dates in the tables. Read 2 November 2026, covering every October addition.
3. [CISA BOD 26-04: Prioritizing Security Updates Based on Risk](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk): Issued 10 June 2026. Replaces BOD 22-01. Applies to federal civilian agencies.
4. [CISA alert: critical zero-day vulnerabilities exploited in Citrix NetScaler ADC and Gateway (27 September 2026, updated)](https://www.cisa.gov/news-events/alerts/2026/09/27/critical-zero-day-vulnerabilities-exploited-citrix-netscaler-adc-gateway)
5. [CISA alert: Ivanti Connect Secure CVE-2026-104935 (13 October 2026)](https://www.cisa.gov/news-events/alerts/2026/10/13/cisa-urges-patching-newly-exploited-vulnerability-ivanti-connect-secure): Says the vendor integrity checker may not detect exploitation.
6. [CISA alert: four vulnerabilities added to the catalog (14 October 2026)](https://www.cisa.gov/news-events/alerts/2026/10/14/cisa-adds-four-known-exploited-vulnerabilities-catalog)
7. [CISA alert: BeyondTrust Remote Support (16 October 2026)](https://www.cisa.gov/news-events/alerts/2026/10/16/cisa-urges-patching-critical-vulnerability-beyondtrust-remote-support)
8. [CISA alert: six vulnerabilities added to the catalog (20 October 2026)](https://www.cisa.gov/news-events/alerts/2026/10/20/cisa-adds-six-known-exploited-vulnerabilities-catalog)
9. [CISA alert: Arista VeloCloud Orchestrator added (23 October 2026)](https://www.cisa.gov/news-events/alerts/2026/10/23/cisa-adds-one-known-exploited-vulnerability-catalog)
10. [Cisco advisory: Secure Firewall ASA and FTD Remote Access SSL VPN denial of service (CVE-2026-76418, 28 October 2026)](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asaftd-tunnel-dos-s6mgkb75): CVSS 8.6, exploited, affected configuration, fixed releases, the secondary-authentication mitigation.
11. [Volexity: chained exploitation of Ivanti Connect Secure zero-days (13 October 2026, updated 29 October)](https://www.volexity.com/blog/2026/10/13/a-series-of-unauthenticated-events-chained-exploitation-of-ivanti-connect-secure-zero-days/): The CVE-2026-104935 chain, the CVE-2026-111357 privilege escalation patched 29 October, and the forensic markers.
12. [Collabora GHSA-g3vx-3m76-fghh: built-in CODE server command injection (CVE-2026-110447)](https://github.com/CollaboraOnline/online/security/advisories/GHSA-g3vx-3m76-fghh): Critical, fixed in built-in CODE server 26.4.303. Published 14 October 2026.
13. [CISA alert: four vulnerabilities added, including F5 BIG-IP APM (22 September 2026)](https://www.cisa.gov/news-events/alerts/2026/09/22/cisa-adds-four-known-exploited-vulnerabilities-catalog): Carries the BOD 26-04 language about checking for compromise before the patch.
14. [Fortinet FG-IR-26-175: FortiMail path traversal (CVE-2026-104286)](https://fortiguard.fortinet.com/psirt/FG-IR-26-175)
15. [Fortinet FG-IR-26-122: CLI path traversal (CVE-2025-61624)](https://fortiguard.fortinet.com/psirt/FG-IR-26-122)
16. [Palo Alto Networks advisory: CVE-2026-0322 (PAN-OS management interface)](https://security.paloaltonetworks.com/CVE-2026-0322)
17. [Cisco advisory: Secure Email Gateway arbitrary file write (CVE-2026-76519)](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-esa-afw-zqYJkjxp)
18. [Cisco advisory: Catalyst SD-WAN Manager API authentication bypass (CVE-2026-76504)](https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sdwan-webauth-xr8beuuU)
19. [MikroTik: September 2026 vulnerability disclosure](https://mikrotik.com/supportsec/september-2026-vulnerability/)
20. [Ahsay: patch announcement for CVE-2026-105133 and CVE-2026-105134](https://www.ahsay.com/en/company/announcements/patch-cve-105133-105134)
21. [JPCERT/CC: SiteGuard Server Edition vulnerability (CVE-2026-106931)](https://www.jpcert.or.jp/at/2026/at260032.html)
