Where Watchtower gets its data
Every advisory on Statamic Watchtower comes from an official source, checked every hour. These are the sources, and the rules I apply to them.
The sources
Statamic, from its own GitHub security advisories. Only Statamic can publish these, so a CVE that Statamic hasn't recognised never appears.
Laravel, from the laravel/framework security advisories.
PHP, from the php-src security advisories.
Redis, from the redis/redis security advisories.
NGINX, from nginx.org's security advisories. That page has no dates, so the date comes from each vulnerability's CVE record.
Node.js, from the Node.js vulnerability blog. Each security release post lists its CVEs with a severity.
Statamic's dependencies, the packages every new Statamic site starts with. That's the Composer packages Statamic's core needs, such as Guzzle, CommonMark and Symfony's YAML component, plus the Composer and npm packages in the default site, such as PHPUnit, Vite and Tailwind CSS. Some of those, like Vite, only run on a developer's machine or when assets are built, so an advisory for them doesn't always affect a live site. Their advisories come from GitHub's advisory database, and the list of packages is read from Packagist every hour, so it follows Statamic when it adds or drops one.
The Linux server (the kernel, OpenSSH, OpenSSL and sudo), from CISA's Known Exploited Vulnerabilities catalogue.
Why the Linux server is handled differently
Ubuntu publishes a notice for every fix, and the kernel alone runs to well over a hundred notices a year, each listing dozens of CVEs. Listing them all would bury the ones that matter. So for the server, Watchtower only lists vulnerabilities that CISA has confirmed attackers are using. Everything else is covered by the server's nightly updates.
What isn't covered
Packages a developer adds to a particular site vary from site to site, so they're best checked site by site, with composer audit and npm audit.
How severity is decided
Severity is the rating the advisory itself gives. Where it doesn't give one, the rating comes from the vulnerability's record at cve.org. A record can rate the same vulnerability under more than one version of CVSS, for example high under CVSS 3.1 and critical under CVSS 4.0. When it does, Watchtower shows the highest.
What "actively exploited" means
Any advisory whose CVE is in CISA's catalogue is marked as actively exploited, whatever its source. CISA only adds a vulnerability when there's evidence of attacks in the wild, so treat these as the most urgent. An older advisory gets the badge if CISA adds it later.
How often it's checked
Every hour. The record goes back to January 2025. This year's advisories are on the main page, and earlier years are in the archive. You can also follow it with the Atom feed.
If you'd rather not keep watch yourself
Watchtower is what I use to keep the sites on my Statamic maintenance plans patched. Critical fixes don't wait for the monthly update.