Skip to content
Reachability Analysis

Triage with evidence asks the cheap questions first and stores every answer

The order follows cost and time

A backlog is a list of version matches. Treating each match as equal spends the week on findings that cannot be exploited here while the few that can wait in the queue. Timing is the reason to hurry. In the 37-CVE ledger on this site, read on 19 Nov 2026, 33 CVEs show dated exploitation. Of those, 24 were exploited within seven days of disclosure (3 of them before it), and the median is 2 days after disclosure.

CISA's BOD 26-04 states the aim as "efficiently prioritizing high-risk vulnerabilities for timely action, while deferring action against low-risk vulnerabilities"; triage here means that sorting. The directive sets remediation urgency from four variables: "Asset Exposure", "KEV Status", "Exploit Automation" and "Technical Impact". Steps 3 and 4 below answer the first two. CISA publishes the other two for each CVE through its Vulnrichment program, and step 4 stores them beside the KEV answer. Two cheaper checks sit in front: whether the affected build is installed at all, and whether the advisory's preconditions hold.

The four-question tool on the home page takes the answers to steps 2 to 4 (code called, service reached, control in front of it, exploitation known) and names the method that settles any open one.

Five steps, who answers each and where each fails

Stop at the first step that fails and write down which one. A step that cannot be answered is recorded as unknown with a next action, never as a pass.

Scroll the table sideways for more columns

StepQuestionSource of the answerWho answersUsually fails when
1Is the affected version or build installed?Inventory, lockfile, package list, appliance versionInventory ownerThe inventory shows the product but not the hotfix level
2Does each advisory precondition hold?Vendor advisory read against the configurationAnalyst with configuration accessThe advisory withholds a condition, or the configuration is read from memory
3Is it reachable from where an attacker can stand?Network path, management-plane exposure, runtime stateNetwork or cloud engineerExposure is assumed from the diagram instead of tested
4Is it exploited, and can it be automated?CISA KEV listing or a dated vendor or research report; Automatable and Technical Impact where CISA or the vendor publishes themAnalyst, by lookupA vendor says "exploitation observed" with no date
5What is the fix, and who changes the asset?Advisory fixed versions, ownership dataAsset ownerThe fixed build for the running release train is not copied exactly

One advisory carried through four Cisco ISE nodes

The advisory is Cisco cisco-sa-ISE-ABP-VNSW7Tn5, CVE-2026-76460: an unauthenticated API request to Cisco ISE or ISE-PIC bypasses the web management interface, and Cisco warns of command execution with root privileges. Cisco published it on 16 Sep 2026 with the statement that its PSIRT is aware of active exploitation. CISA added it to KEV the same day with a due date of 19 Sep 2026 and forensic triage required. CVSS 3.1 base score 10.0. The nodes below are invented for the example; the patch levels, dates and quotations are real.

Opened 16 Sep 2026, four nodes in scope. Node ise-a runs 3.4 with Patch 7 installed, the first fixed patch for the 3.4 train, so it closes at step 1. Node ise-b is a pilot on 3.0, which is end of software maintenance: Cisco gives it no fix and advises moving to a supported release, so it goes to step 5 as a migration. Nodes ise-c (3.2 Patch 8) and ise-d (3.5 Patch 2) are below their trains' fixed patches, 3.2 Patch 11 and 3.5 Patch 4.

Step 2 for ise-c and ise-d: Cisco says the flaw affects ISE and ISE-PIC "regardless of device configuration", so no setting can close it and the only open condition is whether the API can be reached. Step 4 for both: KEV listed, due date 19 Sep 2026, three days after listing. CISA's SSVC data in NVD gives automatable yes and technical impact total, the two other BOD 26-04 variables.

The nodes differ at step 3. ise-c sits behind an infrastructure access control list that admits only the admin VLAN, which is the mitigation Cisco describes. That lowers who can reach the API and does not fix the flaw, so the finding stays open. ise-d serves a guest portal on a network that guests and unmanaged devices can reach. KEV marks forensic triage as required for the CVE, so it applies to both nodes, and BOD 26-04 defines it as remediation or mitigation within three days plus a check whether the system is compromised. The ACL narrows who could reach ise-c but does not show that no admin-VLAN host sent the request, and ise-c was unpatched while exploitation was active. The network team applies the ACL to ise-d on 16 Sep 2026, the security team starts the compromise check on both nodes, and both are upgraded by the due date: 3.2 Patch 11 for ise-c and 3.5 Patch 4 for ise-d.

Outcome: four findings, one closed at step 1 with a reason, one migration ticket, two upgrade tickets with a named owner and the exact target patch, each with a compromise check. CISA's due dates bind US federal agencies; for everyone else they are a benchmark.

The record to store for each finding

Tickets built from this record carry their reasoning, so the assignee does not repeat the analysis. Every field has a date, because a stale answer is the usual reason a closed finding is wrong.

  • Finding: CVE ID, asset name, date opened, analyst.
  • Build: the version found, the command or export it came from, the date it was read.
  • Advisory: URL, the revision date shown on it, and the sentence quoted for each precondition.
  • Preconditions: one line each marked holds, fails or unknown, with the evidence and its date.
  • Reachability: from which networks the interface answers, and how that was tested.
  • Exploitation: KEV added and due dates, or the vendor's statement quoted with its date, or the words "none stated"; Automatable and Technical Impact where published.
  • Fix: the exact target build for this release train, the owner, the change ticket and the due date.
  • Decision: the step reached and the closing reason, or the ticket link.
  • Reopen triggers: advisory revision, a KEV change, or a change to the asset's build or exposure.

When exploitation came first, the patch does not close the finding

BeyondTrust Remote Support CVE-2026-102764 runs the order backwards. The actor exploited a zero-day on 29 Aug 2026, 47 days before the advisory BT26-05 of 15 Oct 2026, and CISA listed it on 16 Oct 2026 with forensic triage required. For a self-hosted instance that was in scope and unpatched in that period, step 4 comes first and a compromise check is part of closing. If compromise is found, rotate every credential the appliance stored or injected. SaaS instances were patched by the vendor, which closes them at step 1.

Unknown is not a pass, and the count of unknowns shows where to invest

For a KEV-listed bug on an internet-facing system, treat an unknown at step 3 as reachable until shown otherwise, because being wrong costs far more than checking. For a local-only bug with no listing, an unknown can wait for the next patch cycle. CVE-2026-80521, a Linux AF_UNIX garbage collector use-after-free, is an example: CVSS AV:L and PR:L mean the attacker needs unprivileged code execution first, and it is absent from KEV release 2026.11.18, with an EPSS of 0.0018.

Count unknowns by step each month. A pile at step 3 means missing network and runtime visibility. A pile at step 5 means missing ownership data.

Where this guide stops

This guide covers the order and the record. Proving that a precondition fails, with the evidence that survives a second reader, is covered in how to prove a finding is not exploitable. Deciding whether code can call a vulnerable function is covered in reachability analysis in practice. Dependency findings have their own guide for step 1 to 3 detail.

Sources

  1. Cisco advisory cisco-sa-ISE-ABP-VNSW7Tn5 (CVE-2026-76460), read 19 Nov 2026
  2. CISA KEV JSON feed, release 2026.11.18, read 19 Nov 2026
  3. CISA BOD 26-04: Prioritizing Security Updates Based on Risk, read 19 Nov 2026
  4. BeyondTrust BT26-05 blog and timeline, read 19 Nov 2026
  5. BeyondTrust advisory BT26-05, read 19 Nov 2026
  6. NVD record for CVE-2026-102764, read 19 Nov 2026
  7. NVD record for CVE-2026-76460, read 19 Nov 2026

Last reviewed 19 Nov 2026.