Skip to content
Reachability Analysis

How Reachability Analysis is written

A ledger record takes its preconditions, affected and fixed versions, mitigation and detection from the vendor advisory. The disclosure date is the advisory date, or the NVD publication date when the advisory has none. The KEV date comes from the CISA feed. The first-exploited date is the earliest dated report of exploitation, from one of four bases, listed here from the most direct to the least: a vendor advisory or release note, a named research firm, the date CISA's SSVC entry in the NVD record marks exploitation as active, and the date CISA added the CVE to KEV. The ledger labels the first two a named report and the last two a CISA date. A CISA date is an upper bound: exploitation cannot have started later than that date, and may have started earlier. When a record has only the KEV addition, its first-exploited date equals the KEV date; the SSVC date can be earlier than the KEV date, as for CVE-2026-46300, where it is 14 May 2026 and the KEV date is 28 Oct 2026.

A statement about what a vendor's product does is labelled the vendor's claim and cites the vendor page. A statement from an outside party is labelled a third-party source. Statements about a method come from its publisher: FIRST for CVSS and EPSS, CISA for the KEV catalog, and vendor documentation for reachability and attack paths.

The editor opens each source before a fact is published, and a claim whose source cannot be opened is left out. A read date is the day the editor opened the source and is shown beside the link. It is not the date the advisory was published or revised, which the record gives separately when the source states it. An empty exploitation field means no dated report of exploitation existed on the read date.

Every record in the second edition was re-read on 19 Nov 2026 against NVD, the CISA KEV feed (version 2026.11.18) and the vendor advisory. When a source changes, the record is revised in place.

Order follows a fixed rule on each page: vendors are alphabetical, CVE records run newest first by disclosure date, and methods are alphabetical. Order never reflects merit, danger or importance.

No exploit code, proof-of-concept steps, payloads or scanning instructions appear anywhere on the site. No page grades a vendor or a method, puts them in an order of merit or names a favorite. CVSS base scores are the ones published in the CVE record by the CVE Numbering Authority that issued the CVE or, where it gave none, by NVD; EPSS values are the ones FIRST publishes.

A vendor may send a newer source for a claim about its own listed method. The record changes to the new page with a new read date, and the change is logged.

Guides are written for a working analyst, use ledger CVEs as worked examples and end with their sources.

Sources

  1. CISA Known Exploited Vulnerabilities catalog, read 19 Nov 2026
  2. FIRST CVSS v4.0 specification, read 19 Nov 2026
  3. FIRST EPSS frequently asked questions, read 19 Nov 2026

Last reviewed 19 Nov 2026.