In development

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.

Get in touch See it work

The matching engine is built. Notifications are not built yet: they come next.

Checked 1,410 vulnerabilities

compared with what you run

Reported 95 findings

  • 26 Critical
  • 36 High
  • 27 Medium
  • 6 Low
The made-up example stack that ships with Vulnsift, on 20 November 2026. Each dot is a vulnerability that was checked, and each square is a finding.

How it works

Findings, not a feed

What follows is the example stack and what the engine said about it on 20 November 2026. The findings are in its own words.

  1. Declare what you run

    List your servers, the software on each one and its version. Say which servers face the internet and which matter most. Today that is a short YAML file.

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

    stack.yml

    assets:
      - name: web1.example.net
        exposure: internet
        criticality: normal
        software:
          - product: nginx
            version: "1.24.0"
            config:
              http2: true
          - product: php
            version: "8.3.12"
          - product: openssh
            version: "8.7p1"
            packaging: distro
      - name: db1.example.net
        exposure: internal
        criticality: high
        software:
          - product: mariadb
            version: "10.11.9"
    Part of the example stack 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. A vulnerability that does not affect your version is not reported.

    vulnsift findings list6 of the 95

    Priority Score Vulnerability Software What to do
    Critical 97 CVE-2026-109618 PHP 8.3.12 web1.example.net Upgrade PHP on web1.example.net to 8.3.36 or later. The vendor also describes a workaround.
    Critical 93 CVE-2026-42945 nginx 1.24.0 web1.example.net Upgrade nginx on web1.example.net to a version later than 1.30.0.
    High 74 CVE-2023-38408 OpenSSH 8.7p1 web1.example.net Check the installed OpenSSH package against your distribution’s advisory for CVE-2023-38408.
    High 71 CVE-2026-49261 MariaDB 10.11.9 db1.example.net Upgrade MariaDB on db1.example.net to 10.11.18 or later.
    Medium 50 CVE-2026-97380 MariaDB 10.11.9 db1.example.net Upgrade MariaDB on db1.example.net to 10.11.19 or later.
    Low 27 CVE-2026-107816 MariaDB 10.11.9 db1.example.net Upgrade MariaDB on db1.example.net to 10.11.19 or later.

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

    The list always ends with what was checked. The one not checked is a control panel that the catalogue does not hold yet.
  3. You get what applies, and what to do

    One finding for each piece of software a vulnerability affects: the reason, a priority, and the fixed version or the vendor’s workaround. The priority depends on your server as well as on the vulnerability, as these three show.

    Known to be exploited, on a server that faces the internet

    Critical score 97 CVE-2026-109618

    PHP 8.3.12 on web1.example.net

    Why it applies
    You run PHP 8.3.12 on web1.example.net (internet-facing). CVE-2026-109618 affects PHP 8.3 up to, not including, 8.3.36. Known to be exploited (CISA KEV, added 26 Oct 2026).
    Why this priority
    • CVSS 9.8 (Critical). CVSS 3.1 scores 9.8 and CVSS 4.0 scores 9.2; using the higher
    • Known to be exploited (CISA KEV, added 26 Oct 2026)
    What to do
    Upgrade PHP on web1.example.net to 8.3.36 or later. The vendor also describes a workaround.
    The vendor’s workaround
    Check the GitHub Security Advisory for mitigation strategies.

    decided by the vendor’s record · declared 8.3.12 · affected 8.3 up to, not including, 8.3.36

    Scored 10.0, on a server that nothing outside can reach

    High score 71 CVE-2026-49261

    MariaDB 10.11.9 on db1.example.net

    Why it applies
    You run MariaDB 10.11.9 on db1.example.net (internal only). CVE-2026-49261 affects MariaDB 10.11.1 up to, not including, 10.11.18.
    Why this priority
    • CVSS 10.0 (Critical)
    • Not reachable from the internet
    What to do
    Upgrade MariaDB on db1.example.net to 10.11.18 or later.

    decided by NVD · declared 10.11.9 · affected 10.11.1 up to, not including, 10.11.18

    A distribution’s package, where the version number cannot settle it

    High score 74 CVE-2023-38408

    OpenSSH 8.7p1 on web1.example.net

    Why it applies
    You run OpenSSH 8.7p1 on web1.example.net (internet-facing), installed from distribution packages. CVE-2023-38408 affects OpenSSH versions before 9.3 upstream; distributions backport fixes without changing that number, so we cannot tell whether this package is fixed. A public exploit is available.
    Why this priority
    • CVSS 9.8 (Critical)
    • A public exploit is available
    • We cannot confirm this version is affected, so this is capped at High
    What to do
    Check the installed OpenSSH package against your distribution’s advisory for CVE-2023-38408.

    decided by NVD · declared 8.7p1 · affected versions before 9.3 · result unknown: a backport is possible

Who it is for

Anyone who runs software and has to read the advisories for it

  • Hosting providers

    Many servers on a handful of stacks, and every advisory raises the same question: which of them does this touch? Declare each server once. A finding names the server, the version it runs and the version that fixes it.

  • Engineers and operations teams

    You know what you run, and you do not have the time to read every CVE published for it. Vulnsift reads the feeds every few minutes and keeps the entries that match your versions, each with the upgrade to make.

  • Organisations with nobody to triage

    A finding is written for whoever looks after the server. It says what is affected, how urgent it is and what to do, each in a plain sentence, so nobody has to interpret a CVSS vector first.

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.

  • The vendor’s record comes first

    The vendor’s own CVE record carries the affected versions on the day of disclosure, so it decides when it can. NVD supplies history and scores. A finding says whose data decided.

  • It stays off your servers

    Vulnsift does not scan, does not log in and asks for no password. It knows what you have told it and nothing more.

Where it is

Built, and next

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.

Next

  • Notifications by Telegram and email: one message for each vulnerability that applies to you, at once or in a digest.
  • 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, and a way to sign up.

Get in touch

Want it for your own stack?

There is nothing to sign up for yet. If you would like to try Vulnsift on what you run, or to ask something about it, write to us and we will reply.

We use what you send to reply to you, and for nothing else.