# For an internet-facing appliance, check the build, the enabled feature and the exposure, then check for compromise even after patching

Guide, 19 Nov 2026, read 19 Nov 2026

**The short answer.** 4 checks settle an appliance finding: read the build from the device, compare it with the vendor's first fixed release in your line, confirm the feature the advisory names is on and reachable, then search for the vendor's indicators. FortiMail, PAN-OS and Cisco ASA/FTD flaws reached CISA's KEV list within a day of disclosure.

## Read the build from the device, not from the asset list

An appliance bundles the operating system, the service and the configuration, so it is patched as one unit and rarely takes a scanner agent. The network or platform team reads the version on the device: get system status on FortiMail, show system info | match sw-version on PAN-OS, and show version on a Cisco ASA or FTD. Paste the output into the ticket with the date.

Then find your release line in the vendor's table. Take the first fixed release for that line. A later release in the same line is fine, and an earlier one is not. PAN-OS fixes are per maintenance branch: a firewall on 11.2.9 sits in the advisory's 11.2.8 up to, not including, 11.2.10-h15 row, so its fix is 11.2.10-h15 or 11.2.16. The step fails when the version is copied from an asset list that was last updated before an upgrade, or when a hotfix suffix is dropped. The table holds the two lines used in the examples here. Every release line is in the ledger entries for [CVE-2026-104286](/ledger/cve-2026-104286/), [CVE-2026-0322](/ledger/cve-2026-0322/) and [CVE-2026-76418](/ledger/cve-2026-76418/).

| Product and CVE | Release line | First fixed release |
| --- | --- | --- |
| FortiMail, CVE-2026-104286 | 7.4 (7.4.0 to 7.4.8 affected) | 7.4.9 |
| PAN-OS, CVE-2026-0322 | 11.2.8 up to, not including, 11.2.10-h15 | 11.2.10-h15 or 11.2.16 or later |

## Confirm the feature is on and the interface is reachable

The security team checks the configuration the advisory names, because it decides whether a vulnerable build is exposed. The first fixed release stays the target either way. The interim control differs by product. The step fails when the check is run on the standby unit of a pair only, or when the setting is read from a template instead of the running device.

- FortiMail: the flaw is unauthenticated and in the GUI component. Check Encryption, IBE, IBE Service in the GUI and whether webmail is reachable from the internet. The advisory does not state IBE as a condition, but its first workaround turns the service off and its log lines name the IBE decrypter. The workaround is config system encryption ibe, set status disable, end. Alternatives are limiting webmail to trusted private networks, or blocking POST requests to /ibe that contain ../ at a web application firewall.
- PAN-OS: Palo Alto Networks states that no special configuration is required to be affected, and "The risk is highest when you allow access to the management interface from external IP addresses on the internet." The attacker also needs a valid high-privilege account on the management interface, so read Device > Administrators and the authentication profiles as well as the permitted IP addresses. The vendor lists no workaround; the [advisory guide](/guides/reading-a-vendor-advisory/) decodes the jump-box and Threat ID text.
- Cisco ASA and FTD: the device is exposed when webvpn is enabled on an interface and a tunnel group uses secondary authentication. Run show running-config webvpn and show running-config tunnel-group, and look for secondary-authentication-server-group in every group, including DefaultWEBVPNGroup. Cisco notes "This check is not limited to profiles that are displayed in the group list on the login page." Cisco lists no workaround. Its mitigation is no tunnel-group-list enable when the default group has no secondary authentication, or no secondary-authentication-server-group when it does, and Cisco recommends the upgrade instead.

## Patching does not show whether the device was already compromised

CISA's BOD 26-04 defines the step: the agency must "carry out a forensic triage of the asset to assess whether the system is compromised". A device that was reachable while the flaw was known to attackers needs that check after the patch, and BOD 26-04 asks "Is the vulnerable asset publicly exposed?" to decide how soon. The security team runs it, searching the full log retention and not only the days since disclosure, and records the search terms, the period and the result. The pace is short: CVE-2026-0322 in PAN-OS was published and listed in KEV on 14 Oct 2026, and Cisco published CVE-2026-76418 on 28 Oct 2026 and CISA listed it on 29 Oct 2026. Each ledger entry holds the vendor's indicators for its product:

- FortiMail: the [CVE-2026-104286](/ledger/cve-2026-104286/) entry lists the source addresses, the system event and encryption log lines, and the archive-account check.
- PAN-OS: the [CVE-2026-0322](/ledger/cve-2026-0322/) entry lists the addresses tied to exploit attempts. An empty search does not show the device is clean.
- Cisco ASA and FTD: the [CVE-2026-76418](/ledger/cve-2026-76418/) entry notes that the advisory publishes no indicators. The effect is a device reload, so compare the uptime line of show version and the reload history with change records.
- BeyondTrust Remote Support: the [CVE-2026-102764](/ledger/cve-2026-102764/) entry holds the BT26-05 timeline. BeyondTrust says the actor rotates infrastructure for every victim, so hunt behavior. If compromise is found, rotate every credential the appliance stored or injected, review new multi-factor registrations on privileged accounts, and image the appliance before rebuilding it.

## A worked case: a FortiMail 7.4.6 gateway, 1 to 7 Oct 2026

Take a gateway running 7.4.6 with webmail published to external recipients. The gateway and its search results are an illustration; the advisory facts are real. Fortinet published FG-IR-26-175 on 1 Oct 2026 as Critical, CVSS v3 9.8, Attack Type Unauthenticated, Known Exploited Yes. CISA added CVE-2026-104286 to KEV the same day, with a due date of 4 Oct 2026 and forensic triage required.

1 Oct: get system status shows 7.4.6, inside 7.4.0 through 7.4.8, and webmail faces the internet. The mail administrator reads Encryption > IBE and finds the service on. Fortinet does not state IBE as a condition of the flaw; the ledger entry infers it from the workaround and the log lines. With an in-range build, an unauthenticated flaw and an exposed interface, the device is treated as affected whatever the IBE reading, and exploitation is already stated. The administrator turns IBE off with the CLI above the same day and saves the configuration before and after.

4 Oct, the CISA due date: the security team searches the system event and encryption logs from the start of retention, 1 Sep 2026, and the firewall and proxy logs for the two indicator addresses. Result: 0 matches for the two indicator addresses in the ledger entry, no archive account the mail team did not create, no cron line running /migadmin, no Invalid Base64 lines. The ticket records the period 1 Sep to 4 Oct 2026, the terms and the result, with the security team as owner. A hit would mean the box is treated as compromised: preserve the logs, rotate administrator and archive credentials, and rebuild from a known-good image. The upgrade to 7.4.9 follows in the booked window.

5 Oct: Fortinet updates the solution table and remediates FortiMail Cloud. For this on-premises box the target is 7.4.9. The change window is booked with the mail team as owner.

7 Oct: the advisory update clarifies that cloud customers need no action. That does not apply to this device.

## When the usual answer is wrong

A configuration check clears a device only when the advisory names a configuration. Palo Alto states that no special configuration is required for CVE-2026-0322, so no setting read can rule out a PAN-OS firewall on an affected build: only the fixed release or a restricted management address changes the answer.

A high availability pair is two devices. The standby holds its own build and its own logs, so read the version on both units, and search the logs of both, because a patched active unit paired with an unpatched standby is exposed after a failover.

Turning off the feature, as the FortiMail workaround does, closes the flaw from that day. It says nothing about the days before, so the compromise search still covers the period from the start of log retention.

## The ticket names the build, the fix and the check owner

Write the answer in the title: product, build in service, first fixed release for the line, exploitation status. For example: FortiMail 7.4.6 gateway, CVE-2026-104286, exploited, upgrade to 7.4.9, compromise search due by a stated date. The body lists the version output, the feature check, the interim control with its date, the indicator search with its period and result, and a named owner for each. Some fixes need an outage window, so the infrastructure owner books it when the ticket opens.

The four-question tool on the home page fits before the ticket: for a flaw on the management plane or webmail, set service reached and control in front from the checks above, and the tool names the method that settles the open answer. Its rule list sends a closed-off management interface to attack-path analysis.

## Related pages

- [How agent investigation records its evidence](/guides/how-agent-investigation-records-its-evidence/)
- [Triaging a dependency finding](/guides/triaging-a-dependency-finding/)
- [Exploitable vs vulnerable](/guides/exploitable-vs-vulnerable/)

## Sources

- Fortinet advisory FG-IR-26-175 (FortiMail): https://fortiguard.fortinet.com/psirt/FG-IR-26-175 (read 19 Nov 2026)
- NVD record for CVE-2026-104286: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-104286 (read 19 Nov 2026)
- Palo Alto Networks advisory for CVE-2026-0322: https://security.paloaltonetworks.com/CVE-2026-0322 (read 19 Nov 2026)
- NVD record for CVE-2026-0322: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-0322 (read 19 Nov 2026)
- Cisco advisory cisco-sa-asaftd-tunnel-dos-s6mgkb75: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asaftd-tunnel-dos-s6mgkb75 (read 19 Nov 2026)
- NVD record for CVE-2026-76418: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-76418 (read 19 Nov 2026)
- BeyondTrust BT26-05 and ARMORY CASTLE: https://www.beyondtrust.com/blog/entry/bt26-05 (read 19 Nov 2026)
- CISA KEV feed, dated 18 Nov 2026: https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (read 19 Nov 2026)
- 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 (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://reachabilityanalysis.com/guides/triaging-an-internet-facing-appliance-finding/
