About Reachability Analysis
The reader in mind is the analyst or engineer holding a scanner finding and a deadline. A severity score says how bad a flaw could be. The question here is narrower: do the conditions that the advisory names exist where you run the software?
Two original assets answer it. The Exploitability Ledger gives, for each of 37 headline CVEs, the preconditions, the affected and fixed versions, the mitigation, the detection and the method that settles exposure: 14 settle on static reachability, 11 on attack-path analysis, 7 on runtime reachability, 3 on agent investigation and 2 on known-exploited evidence. Of the 37, 33 are in the CISA KEV catalog with a dated exploitation report. The Methods Matrix sets seven methods side by side on what each needs, what it proves, what it misses and who offers it.
The guides, listed on the home page, show how to apply both to a finding in your own backlog, using ledger CVEs as worked examples.
Facts come from vendor advisories, the National Vulnerability Database and the CISA Known Exploited Vulnerabilities catalog. How they are sourced, labelled and ordered is set out once, on the editorial policy page.
The first edition appeared on 10 Nov 2026 under the title Is It Exploitable. The second edition, on 19 Nov 2026, uses the title Reachability Analysis. It re-read all 37 records, removed three, and folded 24 ledger entry pages and several guide, method and news pages into the home page, the Methods Matrix or the editorial policy, each answering with a 301. The rows of the folded entries stay in the datasets.
Reach the editor at the address on the contact page. A reader who finds an error is asked to name the page, the claim and a source.
Related pages
Sources
- CISA Known Exploited Vulnerabilities catalog feed, version 2026.11.18, read 19 Nov 2026
Last reviewed 19 Nov 2026.