I built Statamic Watchtower to keep up with security releases
by Stephen Meehan in Statamic, Maintenance Services, News
On 18 November 2026, NGINX, the web server software behind many Statamic sites, fixed ten vulnerabilities. The next afternoon, PHP, the programming language Statamic runs on, published 17 security advisories. Seven of them were rated critical.
Neither could wait for a monthly update. Developers follow these announcements, but the people who own the websites usually don't, so a fix can sit unapplied for weeks without anyone noticing.
Eight places to check
A Statamic site depends on more software than Statamic itself, and each project announces its security fixes in its own way.
Statamic, on its own GitHub security advisories
The packages installed with Statamic's core, in GitHub's advisory database
Laravel, on GitHub
PHP, on GitHub
NGINX, on its own website, without dates
Node.js, in posts on its blog
Redis, on GitHub
The Linux server underneath, in so many operating system notices that the serious ones are easy to miss
I was checking all of these manually, following accounts on X and reading email newsletters on top. I needed one place to pull it all together, so now I just check Statamic Watchtower.
Every advisory comes from an official source and is checked every hour, from each project's own security advisories to CISA's catalogue of exploited vulnerabilities for the server. Where the data comes from lists every source.
What Watchtower does
Every hour, it reads each project's official advisories and adds anything new to one list, newest first. Each item shows:
how severe it is, from low to critical
which software it affects
its Common Vulnerabilities and Exposures (CVE) number, the public ID every vulnerability gets
the versions that fix it
a link to the original advisory
Anything that attackers are already using gets an "Actively exploited" badge. That comes from the Known Exploited Vulnerabilities catalogue kept by CISA, the US Cybersecurity and Infrastructure Security Agency, which only adds a vulnerability once attacks have been seen in the wild.
You can filter by month, software and severity, and there's an archive of earlier years going back to January 2025. If you'd rather not check the page, the Atom feed sends new advisories to any feed reader.
Who it's for
If you're a Statamic developer looking after several sites, it saves you checking eight sources. If you own a Statamic site, it tells you when a fix has been released, so you can ask whoever looks after your site whether it's been applied.
It covers what every Statamic site has in common, including the packages installed with Statamic's core, which you'll find under the Statamic dependencies filter. Packages a developer adds to a particular site vary too much to list, so those are still best checked site by site.
How I use it
When a critical fix appears in Watchtower, I apply it to the sites on my website maintenance plans without waiting for the monthly update.
The sources page lists where every advisory comes from, with links to each one, and explains how severity is decided.
You might also like...
- Patchmageddon and why AI has everyone patching at once
- Every site on my maintenance plans gets the PHP security release this week
- Every site on my maintenance plans gets the NGINX fix this week
- Darkroom 1.4.0 adds favourites and ends the wait between prompts
- Statamic vs WordPress, which suits your business website?
- Do you need the best Statamic agency, or the right developer?
- Why the patch gap on your website matters more now
- Plan your Statamic 5 upgrade while it's still supported
- The importance of website maintenance, and what an out-of-date site can cost
- Your Statamic 3 site still works, but it can't be kept secure