The best open-source vulnerability scanners for Linux in 2026

Updated November 15, 2026By HostCrust10 tools compared14 min read

Trivy is the best open-source vulnerability scanner for most people: one Apache-2.0 binary that checks servers, container images and code against each distribution's own advisories, and in our test the most consistent with the distributions' data. Grype is the best for seeing everything, including CVEs your vendor hasn't fixed, at the cost of the most findings to sort through. HostCrust Patch Proof (ours) is the best second opinion for Ubuntu, Debian, AlmaLinux and Rocky Linux servers: it was the only scanner in our test that reported the running Debian kernel's open CVEs.

For scanning a whole network, use OpenVAS. Lynis is worth running too, but it's a hardening auditor, not a CVE scanner.

Our top picks

Compare at a glance

ToolBest forPricingOpen sourceDeploymentTested by us
Trivyone scanner for servers, container images and codeFree to use under its open-source license (Apache-2.0); Aqua's commercial platform: no public priceYesSelf-hosted CLIYes
Grypeseeing every known issue, including ones with no fix yetFree (open source); Anchore Enterprise: no public priceYesSelf-hosted CLIYes
HostCrust Patch Proof Oursa second opinion on Ubuntu, Debian, AlmaLinux and Rocky serversFreeYesSelf-hosted CLI, or a free web check at hostcrust.com/proofYes
OpenVAS (Greenbone Community Edition)scanning a whole network from one placeFree (Community Edition); OPENVAS BASIC appliance €2,524 per year for fewer than 150 assets; OPENVAS SCAN: contact salesYesSelf-hosted (source build, containers or a free virtual appliance); paid appliancesDocs only
Vulsagentless scanning of many Linux servers over SSHFree (open source); FutureVuls cloud service: no public price (quote)YesSelf-hosted (agentless over SSH, or local)Docs only
OpenSCAPcompliance profiles plus OVAL vulnerability checksFree (open source)YesSelf-hosted CLI (scans the local system)Yes
Wazuhvulnerability detection inside a full security platformFree to self-host (open source); Wazuh Cloud starts at $571 per month for up to 100 agentsYesSelf-hosted or SaaS (Wazuh Cloud)Docs only
OSV-Scannerapplication dependencies and container imagesFree (open source)YesSelf-hosted CLIYes
Lynishardening audits rather than CVE listsFree (open source); Lynis Enterprise SaaS $3 per system per month (one-year term); self-hosted Enterprise: quoteYesSelf-hosted CLI (runs on the host)Yes
Nucleiweb and network exposures, not installed packagesFree (open source); ProjectDiscovery Cloud has a free tier; paid tiers: no public priceYesSelf-hosted CLI (optional ProjectDiscovery Cloud)Docs only

The full ranking

Trivy

Best for: one scanner for servers, container images and code

Trivy is the best all-round open-source scanner: one Apache-2.0 binary that checks container images, filesystems, a live server's root filesystem (trivy rootfs /), repositories and Kubernetes for known vulnerabilities, misconfigurations and secrets. For OS packages it uses each distribution's own advisories, so backported fixes count as fixed. In our study it reported the fewest CVEs on Debian and was the most consistent with the distributions' data: 634 CVEs on a patched Debian 12.15 server, including all 630 the four tools agreed on. Its blind spots were the kernel: none of Debian 12's kernel CVEs, and on AlmaLinux 9.8 all 795 findings were on an old kernel package that wasn't running.

Pricing
Free to use under its open-source license (Apache-2.0); Aqua's commercial platform: no public price (checked November 15, 2026, source)
License
Open source (Apache-2.0)
Deployment
Self-hosted CLI
Runs on
Runs on Linux, macOS, Windows and FreeBSD; OS-package detection for Debian, Ubuntu, RHEL, AlmaLinux, Rocky, Oracle, Amazon Linux, SUSE, Alpine and more

Pros

  • Scans OS packages, language dependencies, images, IaC and secrets
  • Fewest findings on Debian, consistent with distro data, in our test
  • Single binary with official .deb and .rpm packages

Cons

  • Found none of Debian 12's kernel CVEs in our test
  • Judges installed kernel packages, not the running one
  • No unfixed CVEs on AlmaLinux, whose data lists fixes only

Tested by us: Trivy 0.76.2, trivy rootfs / on a Debian 12.15 and an AlmaLinux 9.8 test VM, 14 Nov 2026 (UTC), as part of our scanner study; removed afterwards

Grype

Best for: seeing every known issue, including ones with no fix yet

Grype, from Anchore, casts the widest net: OS packages against each distribution's feed, language packages against GitHub's advisories, plus EPSS, KEV and OpenVEX support. On our AlmaLinux 9.8 server it used Red Hat's data and was the only scanner that showed CVEs with no fix yet: 7,198 that Red Hat lists as affected or won't fix. It also reported the most findings to sort through. A whole-server scan (grype dir:/) matched the kernel image files in /boot against NVD by version string, adding 6,112 CVEs on Debian, most already fixed in the running kernel (2,444 still affect the older installed kernel; 708 are open), plus findings from old .deb files in the apt cache. It needed more than 1.4 GB of RAM and a 3.3 GB database.

Pricing
Free (open source); Anchore Enterprise: no public price (checked November 15, 2026, source)
License
Open source (Apache-2.0)
Deployment
Self-hosted CLI
Runs on
Runs on Linux, macOS and Windows; OS-package matching for Debian, Ubuntu, RHEL, AlmaLinux, Rocky, Oracle, Amazon Linux, SUSE, Alpine, Arch and more

Pros

  • The only scanner in our test that showed unfixed CVEs on AlmaLinux
  • Also flags old and rescue kernels still on disk
  • EPSS, KEV and OpenVEX support

Cons

  • Most findings to sort through: NVD matches on kernel images and cached .deb files
  • Killed for lack of memory on a 1.7 GB VM until swap was added
  • 3.3 GB database on disk

Tested by us: Grype 0.121.3, grype dir:/ on a Debian 12.15 and an AlmaLinux 9.8 test VM, 14 Nov 2026 (UTC), as part of our scanner study (the AlmaLinux run needed a temporary swap file); removed afterwards

HostCrust Patch Proof Ours

Best for: a second opinion on Ubuntu, Debian, AlmaLinux and Rocky servers

Patch Proof is ours. In our study it was the only scanner that reported the running Debian kernel's open CVEs (1,994 with no Debian fix), and the only one that told the running kernel apart from the installed ones. The same study shows its limits. It says nothing about older kernels that can still be booted from GRUB. It can't show unfixed CVEs on AlmaLinux or Rocky, whose data lists released fixes only. And about five hours after its OSV.dev data snapshot, Debian's tracker no longer listed 12 of the CVEs it reported. It covers four distributions and OS packages only, so use it next to a general scanner, not instead of one.

Pricing
Free (checked November 15, 2026, source)
License
Open source (Apache-2.0)
Deployment
Self-hosted CLI, or a free web check at hostcrust.com/proof
Runs on
Ubuntu 20.04–24.04, Debian 11–12, AlmaLinux 8–9, Rocky Linux 8–9

Pros

  • Only scanner in our test to report the running Debian kernel's open CVEs
  • Read-only: installs nothing on the server and needs no root
  • Labels backported fixes and patched-but-not-running kernels

Cons

  • Silent about older kernels that can still boot
  • Can't show unfixed CVEs on AlmaLinux or Rocky
  • Four distributions, OS packages only

Tested by us: Patch Proof 1.0.0 (read-only collector piped over SSH, nothing installed) on a Debian 12.15 and an AlmaLinux 9.8 test VM, 14 Nov 2026 (UTC), as part of our scanner study

OpenVAS (Greenbone Community Edition)

Best for: scanning a whole network from one place

OpenVAS, from Greenbone, is the open-source network vulnerability scanner: it probes every reachable host and service, and with SSH credentials it logs in and checks installed package versions. That makes it the pick for scanning a whole network, including hosts you can't install anything on. The free Community Edition uses the Community Feed; the paid Enterprise Feed adds tests for enterprise products and CIS compliance checks. It's a full stack (scanner, manager and web interface), not a CLI: Greenbone asks for at least 2 CPU cores and 4 GB of RAM, and recommends 8 GB. Paid OPENVAS BASIC appliances start at €2,524 a year.

Pricing
Free (Community Edition); OPENVAS BASIC appliance €2,524 per year for fewer than 150 assets; OPENVAS SCAN: contact sales (checked November 15, 2026, source)
License
Open source (scanner GPL-2.0, gvmd AGPL-3.0); commercial appliances and the Enterprise Feed are proprietary
Deployment
Self-hosted (source build, containers or a free virtual appliance); paid appliances
Runs on
Scanner host on Debian, Ubuntu, Fedora or CentOS Stream (2 CPU and 4 GB RAM minimum); scans any reachable host, with SSH-authenticated checks of Linux patch levels

Pros

  • Scans whole networks, including services without credentials
  • SSH-authenticated checks of Linux patch levels
  • Actively maintained (scanner 23.52.12 on 12 Nov 2026)

Cons

  • Heavier than a CLI: 4 GB of RAM minimum
  • Community Feed lacks enterprise-product tests and compliance policies
  • Greenbone's source-build guide isn't meant for production

Not tested by us yet: based on the vendor's documentation.

Vuls

Best for: agentless scanning of many Linux servers over SSH

Vuls scans Linux and FreeBSD servers over SSH without an agent, or locally, and matches their packages against distro OVAL data, security trackers and NVD, adding exploit and KEV information. Its fast scan needs no root, and the fast-root scan also finds processes that need a restart after updates. Its server mode collects the running kernel version, which most scanners here don't. The cost is setup: it needs separate fetchers and databases (go-cve-dictionary, goval-dictionary and gost) that you keep up to date. Its supported-OS page doesn't list Debian 13 or RHEL 10 yet, though releases continue (0.42.0 on 15 October 2026).

Pricing
Free (open source); FutureVuls cloud service: no public price (quote) (checked November 15, 2026, source)
License
Open source (GPL-3.0)
Deployment
Self-hosted (agentless over SSH, or local)
Runs on
Scans Debian, Ubuntu, RHEL, AlmaLinux, Rocky, Oracle, Amazon Linux, SUSE, Alpine and FreeBSD hosts, plus Windows and macOS

Pros

  • Agentless over SSH; no root for fast scans
  • Finds processes that need a restart after updates
  • Exploit, Metasploit and KEV enrichment

Cons

  • Several databases to fetch and maintain
  • Supported-OS page looks out of date
  • FutureVuls, the commercial service, has no public price

Not tested by us yet: based on the vendor's documentation.

OpenSCAP

Best for: compliance profiles plus OVAL vulnerability checks

OpenSCAP's oscap command evaluates a distribution's OVAL definitions on the local system, and its real strength is compliance: SCAP Security Guide profiles such as PCI-DSS and DISA STIG. On our AlmaLinux 9.8 server it checked all 1,920 definitions in AlmaLinux's OVAL feed in about 2.4 seconds and flagged 82 advisories as missing. Every one was a kernel advisory, matched by an older kernel package still installed next to the patched, running kernel; dnf listed no pending security updates. It's only as current as each vendor's feed, and Red Hat says its OVAL v2 files are in maintenance mode.

Pricing
Free (open source) (checked November 15, 2026, source)
License
Open source (LGPL-2.1; SCAP Security Guide content BSD-3-Clause)
Deployment
Self-hosted CLI (scans the local system)
Runs on
Packaged for RHEL, Fedora, AlmaLinux, Rocky, Debian and Ubuntu; vulnerability scans need the distribution's OVAL feed

Pros

  • Fast and local: no server or database to run
  • Compliance profiles (PCI-DSS, DISA STIG) from SCAP Security Guide
  • Packaged by the RHEL family, Debian and Ubuntu

Cons

  • Flags old installed kernels, not just the running one
  • Depends on each distribution's OVAL feed
  • Red Hat's OVAL v2 data is in maintenance mode

Tested by us: openscap-scanner 1.3.14 (AlmaLinux package) with AlmaLinux's OVAL feed dated 11 Nov 2026, oscap oval eval on an AlmaLinux 9.8 test VM, 14 Nov 2026 (UTC); removed afterwards

Wazuh

Best for: vulnerability detection inside a full security platform

Wazuh isn't a standalone scanner: vulnerability detection is one module of an open-source SIEM and XDR platform. Its agent collects each host's package inventory, and the server matches it against Wazuh's own feed, built from ten Linux vendors' data plus NVD, OSV and CISA. You get continuous, fleet-wide results next to file integrity monitoring and log analysis. The trade-off is weight: an agent on every server and a central server stack to run, or Wazuh Cloud from $571 a month for up to 100 agents. Its docs say systems outside the official list may work but aren't guaranteed full detection.

Pricing
Free to self-host (open source); Wazuh Cloud starts at $571 per month for up to 100 agents (checked November 15, 2026, source)
License
Open source: manager and agent GPL-2.0 (the newer analysis engine AGPL-3.0, some shared libraries dual GPL-2.0 or AGPL-3.0); indexer and dashboard Apache-2.0
Deployment
Self-hosted or SaaS (Wazuh Cloud)
Runs on
Agents for Linux, Windows, macOS, Solaris, AIX and HP-UX; server on 64-bit Linux

Pros

  • Continuous, fleet-wide results
  • Feed built from ten Linux vendors plus NVD, OSV and CISA
  • Also does file integrity monitoring and log analysis

Cons

  • Needs an agent on every host
  • A central server stack to run, or Wazuh Cloud from $571 a month
  • More than you need if you only want a CVE list

Not tested by us yet: based on the vendor's documentation.

OSV-Scanner

Best for: application dependencies and container images

Google's OSV-Scanner is the best free choice for the code you deploy: it reads lockfiles from 11+ language ecosystems and scans container images against OSV.dev, which carries distro advisories as well as language advisories. It isn't built for live servers, and its docs list OS package extraction as container-image only. In our study, its source scan of the Debian 12.15 server still read the dpkg database and reported 653 CVE IDs, 234 of them ones Debian rates unimportant (hidden from its table output). On AlmaLinux 9.8 it found no OS packages at all. It also has an offline mode and call analysis.

Pricing
Free (open source) (checked November 15, 2026, source)
License
Open source (Apache-2.0)
Deployment
Self-hosted CLI
Runs on
Runs on Linux, macOS and Windows; scans lockfiles in 11+ language ecosystems and container images (Alpine, Debian, Ubuntu packages)

Pros

  • Excellent lockfile and container-image coverage
  • OSV.dev data comes from distro and ecosystem advisories
  • Offline mode with a local database

Cons

  • Not designed to scan a live server's packages
  • Found no AlmaLinux packages in our test
  • No paid support plan in its docs

Tested by us: OSV-Scanner 2.7.1, scan source -r over the system directories of a Debian 12.15 and an AlmaLinux 9.8 test VM, 14 Nov 2026 (UTC), as part of our scanner study; removed afterwards

Lynis

Best for: hardening audits rather than CVE lists

Lynis is a security auditor, not a CVE scanner, and CISOfy says as much: it runs hundreds of local checks on configuration, authentication, logging, the kernel and installed tools, then suggests hardening steps. Its vulnerable-package test only counts pending security updates, using your distribution's tools, and lists no CVE IDs. On our Debian 12.15 server, Debian's Lynis 3.0.8 package ran 252 tests in about 12 seconds and gave no warnings and 49 suggestions, but that package test wasn't fully executed because it looks for Ubuntu's apt-check helper. Run it alongside a scanner, not instead of one.

Pricing
Free (open source); Lynis Enterprise SaaS $3 per system per month (one-year term); self-hosted Enterprise: quote (checked November 15, 2026, source)
License
Open source (GPL-3.0)
Deployment
Self-hosted CLI (runs on the host)
Runs on
Linux, macOS, FreeBSD, OpenBSD, NetBSD, AIX, Solaris, HP-UX and other Unix systems

Pros

  • Hundreds of hardening checks in seconds
  • Runs from a tarball; nothing to install
  • Free (GPL-3.0)

Cons

  • Lists no CVE IDs
  • Vulnerable-package test incomplete on Debian (needs apt-check)
  • Debian 12 ships 3.0.8, behind upstream 3.1.7

Tested by us: Lynis 3.0.8 (Debian package) on a Debian 12.15 test VM, 14 Nov 2026 (UTC): lynis audit system --quick; purged afterwards

Nuclei

Best for: web and network exposures, not installed packages

Nuclei, from ProjectDiscovery, sends YAML-template probes over HTTP, DNS, TCP, SSL and other protocols, and ProjectDiscovery says the template set it loads by default holds about 13,600 community and in-house templates. That makes it strong at what an attacker sees from outside: an exposed admin panel, a vulnerable web app version, a leaky service. It doesn't look at installed OS packages, so it won't tell you whether a server's OpenSSL or kernel is patched. It's MIT-licensed and a single binary, with a free tier on ProjectDiscovery's cloud. Its README warns that running it as a service may pose security risks.

Pricing
Free (open source); ProjectDiscovery Cloud has a free tier; paid tiers: no public price (checked November 15, 2026, source)
License
Open source (MIT)
Deployment
Self-hosted CLI (optional ProjectDiscovery Cloud)
Runs on
Runs on Linux, macOS and Windows; probes network and web targets over HTTP, DNS, TCP, SSL and more

Pros

  • Fast, template-driven checks of what attackers can see
  • Large community template library
  • MIT license, single binary

Cons

  • Doesn't check installed packages
  • Results are only as good as the templates
  • Paid cloud tiers have no public price

Not tested by us yet: based on the vendor's documentation.

How we picked

This page is about scanners you can run on, or against, Linux servers without paying for a license. We ranked them on four things:

  1. Accuracy on a real server. Does it use the distribution's own fix data, so backported fixes count? Does it know which kernel is running? Does it stay out of leftover files?
  2. Coverage. OS packages, language dependencies, container images, network services, or a mix.
  3. Effort. A single binary, or a stack with databases and feeds to maintain.
  4. Health. A recent release, an open license, and documentation that matches the code.

Six of the ten ran on our test servers on 14 Nov 2026 (UTC): Trivy, Grype, OSV-Scanner and Patch Proof in a side-by-side study on a fully patched Debian 12.15 VM and an AlmaLinux 9.8 VM, plus Lynis and OpenSCAP. OpenVAS needs more memory than those 2 GB VMs have; Vuls needs several databases built first; Wazuh needs a server stack; Nuclei doesn't look at installed packages. Those four are ranked from their documentation. Patch Proof is ours and is marked “Ours”. It's ranked third: it won on one measured point, stated on its card, and the same study found real limits, listed there too.

What we saw on our test servers

Both test servers were fully patched by their own automatic updates, so nothing should be fixable, and on Debian all four scanners in our study agreed: no installed package had a fix waiting. They disagreed on everything else. The counts below are from our full scanner comparison, which checks every Debian disagreement against Debian's tracker.

ScannerDebian 12.15: CVEs reportedOf which kernelAlmaLinux 9.8: CVEs reported
Trivy 0.76.26340795, all on an old kernel package that isn't running
Grype 0.121.38,1266,112, matched from kernel image files through NVD12,598, including 7,198 Red Hat lists as unfixed or won't fix
OSV-Scanner 2.7.1653 (234 rated unimportant by Debian)00 (“No package sources found”)
Patch Proof 1.0.0 (ours)2,6431,994, for the running kernel0

On Debian, all four agreed on 630 CVEs in installed user-space packages, none with a Debian fix yet. Almost all of the rest comes down to two things: which kernel each tool checks, and whose data it trusts. Trivy, OSV-Scanner and Grype's package matcher never linked Debian's kernel packages to Debian's kernel records, so only Patch Proof reported the running kernel's open CVEs. Grype matched the kernel image files by version string instead; of its 6,112, Debian's tracker shows 708 really open and the rest fixed or never affected. On AlmaLinux, Grype used Red Hat's data and was the only tool to show unfixed CVEs; Trivy flagged only the old kernel; Patch Proof reported nothing. One honest note: none of the scanners reported a CVE as open because of a backported fix, so that classic problem didn't show up on these two servers.

Our own two runs told the same story from other angles. OpenSCAP flagged 82 AlmaLinux kernel advisories that all came from the old kernel package; dnf updateinfo list --security listed none pending:

$ oscap oval eval --results results.xml alsa-9.xml > eval.txt
$ grep -c ': true' eval.txt
82
$ rpm -q kernel-core
kernel-core-5.14.0-570.12.1.el9_6.x86_64
kernel-core-5.14.0-687.66.2.el9_8.x86_64
$ uname -r
5.14.0-687.66.2.el9_8.x86_64

Lynis finished 252 hardening tests in about 12 seconds on Debian, but its log shows the vulnerable-package test couldn't run there:

Performing test ID PKGS-7392 (Check for Debian/Ubuntu security updates)
Result: apt-check (update-notifier-common) not found
Result: test not fully executed (missing apt-check output)

Why do vulnerability scanners disagree?

Scanners disagree because they read different data about different files. First, version numbers: Debian, Ubuntu and the RHEL family fix most CVEs by backporting a patch into the version they already ship, so a scanner that compares upstream versions (NVD's CPE ranges, for example) reports issues that are fixed. Scanners that use the distribution's own advisories avoid this: none of the three we ran did it for installed packages in our test, though Grype's NVD matching of kernel image files and cached .deb files did something similar. Second, the kernel: a server can have two or three kernel packages installed and run only one, and most scanners judge every installed package. Third, stray files: old .deb or .rpm files in a package cache and kernel images in /boot look like software to a directory scan. Fourth, timing: each tool's database was built at a different hour, and advisories change during the day. Fifth, unfixed issues: some tools list CVEs your vendor hasn't fixed or won't fix; others list only fixes you can install. None of these are bugs exactly, but they decide what lands on your to-do list.

Host scanners, network scanners and auditors

TypeWhat it looks atTools hereGood for
Host package scannerThe installed package databaseTrivy, Grype, Patch Proof, Vuls, OpenSCAP, Wazuh“Which known CVEs affect this server?”
Dependency and image scannerLockfiles, SBOMs, container imagesOSV-Scanner, Trivy, GrypeCI pipelines and container registries
Network scannerOpen ports and services, plus SSH loginsOpenVAS, NucleiMany hosts, and what an attacker sees
AuditorConfiguration and hardeningLynis, OpenSCAP (compliance profiles)Hardening and compliance checklists

Most teams need one host scanner and, once there are more than a handful of hosts, one network scanner. An auditor is a cheap extra.

What to look for in a Linux vulnerability scanner

  • Distribution data, not just NVD. Your distro's tracker knows which package version fixed each CVE for your release, including backports.
  • Running-kernel awareness. Kernel CVEs were the biggest group on both our test servers. A scanner should say whether the kernel you're running is affected, not just one that's installed.
  • Clear statuses. “Fix available”, “no fix yet” and “won't fix” need different actions. Tools that merge them bury the few things you can fix today.
  • Your distros and versions. Check the coverage list: Trivy's table stops at Debian 12 and Rocky 9 for now, and Patch Proof covers four distros.
  • Footprint. A single binary is easy to run from cron. A network scanner or SIEM needs its own server and RAM.
  • Data freshness. How often the database updates, and whether you can run offline.

Open source or commercial?

The open-source scanners here are not toys: Trivy, Grype and OpenVAS sit underneath commercial products from Aqua, Anchore and Greenbone. What the paid versions add is mostly around the scan: a central dashboard for many hosts, scheduling, ticketing, support with an SLA, and (for Greenbone) a commercial vulnerability feed with more tests. If you run a few servers and are comfortable with a cron job and a report, the open-source tools cover the detection itself. The cost shows up elsewhere: OpenVAS and Wazuh need a server with real memory, and someone has to keep feeds and databases current. If you need to show an auditor trends across hundreds of assets, or you want someone to call, look at our ranking of vulnerability management software, where Tenable, Qualys, Rapid7 and others are compared with their published prices.

Do you need a vulnerability scanner at all?

If your servers patch themselves daily and you reboot after kernel updates, a scanner mostly confirms that, and that confirmation is the point. Automatic updates fail silently: a held package, a masked timer, a third-party repository with no security data, or a kernel installed but never booted. A weekly scan of each server catches those, and it gives you evidence when a customer or auditor asks. Your distribution already ships basic tools: dnf updateinfo list --security on the RHEL family and debsecan on Debian list known issues from the distribution's own security data. A dedicated scanner adds CVE detail, the kernel question, container images and history. For one or two servers, a monthly check is plenty; for a fleet, run one daily and only look at what changed. Containers are a separate question: if you ship images, scan them in CI before they reach a server.

How we checked this: Our scanner study ran Trivy 0.76.2, Grype 0.121.3, OSV-Scanner 2.7.1 and HostCrust Patch Proof 1.0.0 against a fully patched Debian 12.15 test VM and an AlmaLinux 9.8 test VM on 14 Nov 2026 (UTC), with checksum-verified release files. The same day we ran Lynis 3.0.8 (Debian's package) on the Debian VM and OpenSCAP 1.3.14 with AlmaLinux's OVAL feed on the AlmaLinux VM. Everything was removed afterwards. OpenVAS, Vuls, Wazuh and Nuclei are researched from their documentation and were not run on our servers. Anything we didn't run ourselves comes from the official documentation listed under Sources.

Check which CVEs are really open on your server

HostCrust Patch Proof compares every installed package with your distribution's own security data. It counts fixes your distro backported and checks the kernel that is actually running, not just the one on disk. Read-only, no root, free.

Run the free check About Patch Proof

FAQ

What is the best free vulnerability scanner for Linux servers?

Trivy, for most people: it's free (Apache-2.0), installs from a .deb or .rpm, and trivy rootfs / scans the server it runs on using the distribution's own advisories. If your servers run Ubuntu, Debian, AlmaLinux or Rocky Linux, add HostCrust Patch Proof (ours, free) to check kernel CVEs against the running kernel. To scan many hosts over the network, use OpenVAS (Greenbone Community Edition).

Is OpenVAS still free?

Yes. Greenbone's Community Edition, which includes the OpenVAS scanner, is open source (the scanner is GPL-2.0, the manager AGPL-3.0) and uses the free Community Feed. Greenbone sells the Enterprise Feed and OPENVAS appliances on top; OPENVAS BASIC starts at €2,524 a year for networks under 150 assets. Plan for at least 2 CPU cores and 4 GB of RAM.

Is Lynis a vulnerability scanner?

Not in the CVE sense. Lynis audits configuration and hardening. Its vulnerable-package test counts pending security updates using your distribution's tools and doesn't list CVE IDs. On our Debian 12 server that test wasn't fully executed, because it looks for Ubuntu's apt-check helper. Use Lynis for hardening and a scanner such as Trivy for CVEs.

Trivy or Grype: which is better?

Both are free, Apache-2.0 and use each distribution's own security data for OS packages. Trivy also finds misconfigurations, secrets and license issues, so it's the better single tool. Grype focuses on vulnerabilities, adds EPSS and KEV data, and shows vendor statuses such as “fix deferred” and “won't fix”. In our test, Grype's whole-server scan also matched kernel images and cached .deb files, which added thousands of mostly fixed CVE IDs, and it needed more memory than our 1.7 GB VM had.

Why does my scanner report CVEs my distribution already fixed?

Usually one of four reasons. The scanner compares upstream version numbers and misses a fix your distribution backported; none of the three scanners we ran did this for installed packages in our test, though Grype's NVD matching of kernel image files did something similar. It flags an old kernel package that is still installed but no longer running. It reads leftover package files, such as the apt cache. Or its data is a few hours older or newer than another tool's. Check the CVE on your distribution's own tracker, which records the fixed package version for your release.

Can OSV-Scanner scan a Linux server?

Not as its main job. OSV-Scanner is built for lockfiles and container images, and its docs list OS package extraction as container-image only. In our study, its source scan of a Debian server did read the dpkg database, but on AlmaLinux it found no OS packages at all. For a live server, use Trivy, Grype, Vuls or Patch Proof.

Sources

  1. Trivy docs: rootfs target (scanning a host)
  2. Trivy docs: vulnerability scanner (vendor advisories, backports, precise and comprehensive modes)
  3. Trivy v0.76.2 release
  4. Grype docs: vulnerability data by ecosystem
  5. Grype on GitHub
  6. OSV-Scanner docs: supported artifacts (OS packages are image-only)
  7. Greenbone Community Edition docs: source build and hardware requirements
  8. Greenbone: Community Feed vs Enterprise Feed
  9. Greenbone OPENVAS BASIC order page (price)
  10. Vuls on GitHub (scan modes, data sources)
  11. Vuls docs: manual install (go-cve-dictionary, goval-dictionary, gost)
  12. Vuls docs: server mode (running kernel)
  13. OpenSCAP user manual
  14. Red Hat security data (OVAL v2 in maintenance mode)
  15. Canonical: Ubuntu OVAL data
  16. Wazuh docs: how vulnerability detection works
  17. Wazuh Cloud pricing
  18. Lynis by CISOfy
  19. Lynis control PKGS-7392 (vulnerable packages)
  20. Nuclei on GitHub
  21. ProjectDiscovery: open-source tools (nuclei-templates: about 13,600 templates, about 4,400 for CVEs)
  22. HostCrust Patch Proof on GitHub