Every morning I get a Telegram message with the CVEs that matter to my clients. Not the 150+ CVEs published daily by NIST — just the ones relevant to the technologies my consulting clients actually run: FortiGate, SonicWall, Palo Alto, pfSense, Windows Server, and a handful of others.
The script that does this is 50 lines of Python. It has been running in a cron job for over a year without meaningful issues. Here is how it works and what I learned building it.
The problem with raw CVE feeds
NIST publishes everything. That is their job. On a busy day the NVD feed has 200+ entries. If you subscribe to the RSS feed without filtering, you will either stop reading it or you will miss the one entry that matters.
The problem I needed to solve was not access to CVE data — it was relevance filtering at the point of ingestion.
