Tell us what you run. We’ll tell you what matters.

Vulnsift checks the software you declare, down to the version, against the CVE List, NVD, CISA KEV and EPSS. It reports the vulnerabilities that apply to what you run, and says of each one why it applies, how urgent it is and what to do.

The matching engine is built. Notifications come next.

Critical score 90 CVE-2026-123633

nginx 1.24.0 on web1.example.net

Why it applies
You run nginx 1.24.0 on web1.example.net (internet-facing). CVE-2026-123633 affects nginx 1.19.7 and later, fixed in 1.30.7 and 1.31.9. A public exploit is available.
What to do
Upgrade nginx on web1.example.net to 1.30.7 or later.

95 findings from 4 software instances checked against 1410 vulnerabilities; 1 not checked.

What the engine says about the made-up example stack that ships with it, on 20 November 2026. The wording is its own.

How it works

Findings, not a feed

  1. Declare what you run

    List your servers, the software on each one and its version. Today that is a short YAML file.

  2. Vulnsift compares it

    Each version, edition and enabled feature is compared with the affected ranges in the vendor’s CVE record and in NVD. CISA KEV says whether a vulnerability is known to be exploited, and EPSS how likely that is.

  3. You get what applies

    One finding for each piece of software a vulnerability affects: the reason, a priority, and the fixed version or the vendor’s workaround. A vulnerability that does not affect your version is not reported.

Vulnsift does not scan your servers or log in to them. It works from what you tell it.

What you can rely on

It shows its working

  • It explains itself

    A finding names the version you run and the versions that are affected, and every verdict keeps the evidence it was made on.

  • It says what it checked

    Every report ends with what was compared and what was not. Vulnsift never tells you that a stack is “secure”; it tells you what was checked and what was found.

  • Rules decide the priority

    Priority comes from fixed rules over CVSS, exploit evidence, how exposed the server is and how much it matters. No language model matches, scores or states a fact about a vulnerability.

  • It says when it cannot tell

    A package from a Linux distribution may carry a fix that its version number does not show. Vulnsift reports such a case only when there is exploit evidence, and says that it cannot tell.

Where it is today

Built, and planned

Built

  • The matching engine, with a command line and a JSON API.
  • Feeds that keep themselves current: the CVE List every 5 minutes, NVD and CISA KEV every 10, EPSS twice a day.
  • A catalogue of 23 products, among them nginx, Apache, PHP, MySQL, MariaDB, WordPress, cPanel, OpenSSH and OpenSSL.

Planned

  • Notifications by Telegram and email.
  • A script you run on your own server that reports what it runs. It is read-only and prints what it will send.
  • A web interface.

There is nothing to sign up for yet.