nday

About nday

nday draws each vulnerability's lifecycle as a timeline: disclosure, patch, technical analysis, public PoC, exploitation in the wild, CISA KEV. The home page lists vulnerabilities that just reached a new stage; each vulnerability page gives every event's source, time precision and raw data.

If nday doesn't know, it says so. Events without a source time are marked “time unknown”; inferred stages (such as exploitation inferred from KEV) get only an upper bound and name their basis; bulk-imported data never poses as live observation. Sources: ~/src.

The site sets cookies only when you sign in, and loads nothing from third parties.

This product uses data from the NVD but is not endorsed or certified by the NVD.

Contact: [email protected].

Comments on vulnerability pages follow these rules: Community rules

Ordering and pinning on the home page

The home list (~/) is ordered by when each vulnerability last reached a new stage, newest first. For each kind of lifecycle event nday takes its earliest known time, and the latest of those times places the vulnerability; on equal times the one at the higher current stage comes first.

Once a kind of event has a known time, further events of that kind, such as another advisory with a patch or another PoC, never move the vulnerability up again. Events whose time is unknown (the source gave none and nday did not observe them live) do not count as a change, and neither do posts to the oss-security mailing list.

By default the list covers the last 7d and only vulnerabilities whose latest change is to PAT or a later stage, so a newly published CVE alone does not appear; --since and --min-stage change this. CVE records marked REJECTED are left out unless --include-rejected is on.

On the first page, nday pins up to 10 vulnerabilities that researchers are discussing right now above the list. A vulnerability is pinned only when all of the following hold.

  • At least 2 different researchers on nday's list posted about it on X in the last 7d.
  • Its latest researcher post is from today or the 3 UTC days before.
  • Its current wave of discussion began today or in the 7 UTC days before. A wave is a run of posts on UTC days at most 7 days apart: a vulnerability discussed again after a longer silence can be pinned again, and one discussed without such a break stops being pinned 7 days after the day its wave began.
  • It would be in the list you are viewing anyway: same window, minimum stage, rejected switch and tags.

Pinned rows are ordered by the number of researchers, then by the latest post. If fewer qualify than the limit, the rest is filled from the top of the discussed ranking, whatever the window or minimum stage. Pinned rows appear only on the first page and are not repeated among the ordinary rows.

The numbers above are the settings in force now.

Keyboard shortcuts

j / k
move the cursor between list rows or events
Enter
open the vulnerability under the cursor
/
focus the search box (Esc to leave)
y
copy the CVE ID
o
vulnerability page: open the source of the event under the cursor
u
go back
?
show or hide the shortcut help

Shortcuts are off while you type in a field, and while Ctrl, Alt or ⌘ is held.