nday

Acerca de nday

nday representa el ciclo de vida de cada vulnerabilidad como una cronología: divulgación, parche, análisis técnico, PoC pública, explotación activa e inclusión en el KEV de CISA. La portada muestra las vulnerabilidades que acaban de entrar en una nueva etapa; la página de cada vulnerabilidad indica la fuente, la precisión temporal y los datos en bruto de cada evento.

La norma: lo que no se sabe, se dice. Los eventos cuya fuente no da fecha se marcan con fecha desconocida; las etapas inferidas (como la explotación inferida a partir del KEV) solo llevan un límite superior y citan su fundamento; los datos importados en bloque nunca se presentan como observados en tiempo real. Fuentes: ~/src.

El sitio no carga recursos de terceros.

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

Contacto: [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.

Atajos de teclado

j / k
mover el cursor entre las filas de la lista o los eventos
Enter
abrir la vulnerabilidad bajo el cursor
/
ir al cuadro de búsqueda (Esc para salir)
y
copiar el identificador CVE
o
en una vulnerabilidad: abrir la fuente del evento bajo el cursor
u
volver atrás
?
mostrar u ocultar la ayuda de atajos

Los atajos se desactivan al escribir en un campo y mientras se mantiene presionada Ctrl, Alt o ⌘.