←Back to Knowledge

"Is our version safe?" is the question clients ask most. Our free Patch Tracker shows the safe version and fixed CVEs for 16 platforms, checked hourly.

Date
Reading
2 min read
Written by
Nick Li
Tags
#Risk#Engineering

Over the past few months, one question has come up in our inbox more than any other: "Is the version we're running safe?"

It usually arrives right after a headline. PHP2Shell, the OpenSSH flaw on Alpine servers, another Node.js security release. A business owner reads the news, asks their developer, and the developer has to check several vendor websites, changelogs and vulnerability databases to give a straight answer. We've done that check for clients many times, so we decided to put the answer on one page, for everyone.

Introducing the Patch Tracker

The Patch Tracker is a free table on our website. For each language, framework and platform, it shows:

  • Last update: when the newest release came out.

  • Fixed vulnerabilities: the CVEs fixed in the latest security release. Click one to open its official record on cve.org.

  • Safe version per branch: the newest release on each version line that still gets fixes, so you can stay on your branch (PHP 8.3, Node.js 22…) and still be up to date.

  • History: expand a row to see the last three security releases and when each branch stops getting support.

Branches marked EOL no longer get security fixes, and long-term support branches are marked LTS.

It covers Node.js, PHP, Python, Java, Go, .NET, Ruby, Rust, React, Next.js, Vue, Nuxt, WordPress, Drupal, the Linux kernel and Ubuntu. The data comes from the vendors' own security advisories and release lists and is checked every hour, so you don't have to remember to look.

How to use it in two minutes

  1. Find out what you run. Ask your developer or hosting provider, or check yourself:
php -v        # PHP
node -v       # Node.js
python3 -V    # Python
java -version # Java
lsb_release -a  # Ubuntu
  1. Find your branch in the table. If your version is lower than the safe version on that branch, an update is due.

  2. Check for EOL. If your branch is marked EOL, a simple update isn't enough: plan a move to a supported branch.

For WordPress, the version is shown at the bottom of the dashboard. Remember that plugins and themes need updating too; the table covers WordPress itself.

What it can't do

The table tells you which versions have the fixes that are publicly known today. It doesn't scan your website or server, and new flaws are found all the time, so a safe version today may need another update next month. It is a quick reference, not a security audit.

If you'd like to know more about why version numbers matter, our article on PHP2Shell is a good example of how quickly an old version becomes a real risk.

Bookmark the Patch Tracker and check it whenever a security headline makes you wonder.

If you're not sure what your systems run, or you'd like help updating them, let's talk.

Further reading