Contact Reachability Analysis
Three kinds of message are useful. The first is a correction: quote the line as printed, say what is wrong and give one address that shows the right fact. The second is a news tip, with a link to the primary page, such as an advisory or a catalog entry. The third is a request for the datasets.
The Exploitability Ledger and the Methods Matrix are published as CSV and JSON on the home page. If you want a different cut of them, say which fields you need. Reuse is under CC BY 4.0 with the cite line printed on that page.
To ask for a CVE to be added to the ledger, send the CVE identifier and the vendor advisory. The ledger holds 37 headline CVEs disclosed from 9 Apr to 5 Nov 2026, so say why the bug belongs among them. A request is not a promise to add it.
Questions about how a record was built are welcome. The answer points to the advisory, the NVD entry and the KEV entry the record draws on, with the read date.
Vendors may send a factual correction to their own listed claims, with a link to the page that supports it.
Please do not send exploit code, proof-of-concept material or scan results. If you have found a flaw in a product, report it to the vendor named on that product's advisory.
The site has no forms, accounts or mailing list, so email is the only way to reach the editor.
Related pages
Sources
- Creative Commons Attribution 4.0 International, read 19 Nov 2026
Last reviewed 19 Nov 2026.