Skip to Content (Press Enter)
Is your Statamic site hiding the pain like Harold? Find out

I built Statamic Watchtower to keep up with security releases

Statamic Watchtower lists every security release for the software a Statamic site runs, in one place, checked every hour. I built it for my own maintenance work, and it's free for anyone to use.

by Stephen Meehan in Statamic, Maintenance Services, News

Collage of a watchtower casting a blue light beam over dark server racks, styled with photocopier grain and diagrams.

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.

  1. Statamic, on its own GitHub security advisories

  2. The packages installed with Statamic's core, in GitHub's advisory database

  3. Laravel, on GitHub

  4. PHP, on GitHub

  5. NGINX, on its own website, without dates

  6. Node.js, in posts on its blog

  7. Redis, on GitHub

  8. 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.

19th November, 2026 by Stephen Meehan in Statamic, Maintenance Services, News
.

Get a measurably better website

Your online presence matters, increase engagement, lower bounce rates, and improve conversions.
Statamic Websites