Free tool · Patch Proof

See which CVEs are really open on your Linux server

Scanners that compare version strings flag fixes your distro already backported, and miss patched kernels that were never rebooted into. Patch Proof checks every installed package against your distro's own security data and splits the results into what's really open, what's fixed by a backport, and what's patched on disk but not running.

Read-onlyNo rootNothing installedInventory not stored

Ubuntu 20.04, 22.04 and 24.04 · Debian 11 and 12 · AlmaLinux 8 and 9 · Rocky Linux 8 and 9

1 Run the collector on your server

It's a short shell script. Read it first: it prints package and OS metadata only, with no hostname, no IP address, no users and no file contents other than /etc/os-release. It needs no root and no network.

curl -fsSLO https://hostcrust.com/collect.sh
less collect.sh                  # about 50 lines: read it before you run it
sh collect.sh > inventory.txt

Or from your laptop: ssh your-server 'sh -s' < collect.sh > inventory.txt

Prefer to keep everything local? The same engine is open source: HostCrust Patch Proof on GitHub. Also free: unattended-upgrades-check, which checks that auto-patching is really working.

Show the full collector script
#!/bin/sh
# HostCrust Patch Proof collector, v1. Apache-2.0. https://hostcrust.com
#
# Read-only. Needs no root and no network. Installs nothing, writes nothing.
# Prints package and OS metadata only: no hostname, no IP address, no users,
# and no file contents other than /etc/os-release.
#
# Usage:  sh collect.sh > inventory.txt
#         ssh host 'sh -s' < collect.sh > inventory.txt

LC_ALL=C
export LC_ALL

echo "# hcproof-collector 1"

echo "## os-release"
cat /etc/os-release 2>/dev/null

echo "## kernel"
echo "release=$(uname -r)"
echo "build=$(uname -v)"
echo "arch=$(uname -m)"
# Ubuntu only: the exact package version of the running kernel.
[ -r /proc/version_signature ] && echo "signature=$(cat /proc/version_signature)"
# Installed kernel images (file names only).
for f in /boot/vmlinuz-*; do [ -e "$f" ] && echo "image=${f#/boot/vmlinuz-}"; done

echo "## reboot-required"
if [ -e /var/run/reboot-required ]; then
    echo "flag=yes"
    [ -r /var/run/reboot-required.pkgs ] && sed 's/^/pkg=/' /var/run/reboot-required.pkgs
else
    echo "flag=no"
fi

echo "## packages"
if command -v dpkg-query >/dev/null 2>&1; then
    echo "format=dpkg"
    # status, binary name, version, architecture, source ("name" or "name (version)")
    dpkg-query -W -f='${Status}\t${Package}\t${Version}\t${Architecture}\t${Source}\n'
elif command -v rpm >/dev/null 2>&1; then
    echo "format=rpm"
    # name, epoch, version, release, architecture, source rpm, vendor
    rpm -qa --qf '%{NAME}\t%{EPOCH}\t%{VERSION}\t%{RELEASE}\t%{ARCH}\t%{SOURCERPM}\t%{VENDOR}\n'
else
    echo "format=none"
fi

echo "## end"

2 Paste or upload the output

The collector output, or a plain dpkg -l / rpm -qa list (then choose the OS below).

We build the report in memory and don't store your inventory. Privacy notice

What it finds on a real server

Ubuntu 24.04 serverOpen, patch availableFixed by backportPatched, not running
Still on its release kernel (6.8.0-31)9,261 (9,257 in the kernel)7770
After apt full-upgrade and a reboot (kernel 6.8.0-149)4 (Ubuntu Pro only)10,0340

Measured on 14 Nov 2026 with the same OSV data snapshot. After the update, 10,034 CVEs are fixed by backports: the kernel version still reads 6.8.0, which is why tools that only compare version strings report them as open.

Questions

How is this different from a vulnerability scanner?

Many scanners compare the upstream version number with the version where upstream fixed a bug. Distros often fix the bug in their own build without changing the upstream version, so those scanners report it as open. Patch Proof compares against the distro's own fixed build, says which fixes were backported, and checks which kernel is actually running.

Is it safe to run on production?

The collector only reads package metadata (dpkg-query or rpm -qa), /etc/os-release, uname -r and the reboot-required flag. It writes nothing, needs no root and makes no network connection. The whole script is shown above.

Where does the vulnerability data come from?

From OSV.dev, which publishes the Ubuntu, Debian, AlmaLinux and Rocky Linux security data in one format. We refresh it daily, and every report states the date of the data it used.

What doesn't it cover?

Containers and images, language packages (pip, npm and so on), and packages from third-party repositories, which are listed as "not assessed". Debian 11 data is incomplete since its long-term support ended, and the AlmaLinux and Rocky Linux data doesn't list unfixed issues.

Can I run it without sending you anything?

Yes. HostCrust Patch Proof is open source (Apache-2.0) on GitHub: github.com/HostCrust/patch-proof. Install it with pipx install git+https://github.com/HostCrust/patch-proof and run hc-proof collect --script | ssh your-server sh -s | hc-proof report --input - --out report.html. The inventory never leaves your machine.