CVE Check – “Staying Secure & Up to Date” (Series Overview)
The trigger was close to home: in October/November 2026, two things unsettled many homelab operators – actively exploited CVEs (e.g. the PHP2Shell flaw) and updates that only arrived “halfway” (a well-known image tag briefly shipping a vulnerable version again; packages that stop receiving security updates entirely without the distribution’s free add-on subscription). Instead of panic, a system helps: inventory → scan → compare → automate → routine. That’s exactly what this series builds, part by part – hands-on, with real examples.
There’s another reason this topic keeps growing: modern AI lowers the barrier for attackers. AI tools help find flaws faster, craft deceptively real phishing and malware, and adapt attacks automatically. Even small, unremarkable systems become more frequent targets – so if you don’t have your updates under control, you move into the spotlight faster.
The parts (released roughly every 2–3 days)
| Part | Topic | Planned |
|---|---|---|
| 0 | Series overview (this page) | Today |
| 1 | Why CVE alerts should concern you | 05 Nov |
| 2 | Inventory – know your systems | 07 Nov |
| 3 | Toolbox: scanners, databases & sources | 10 Nov |
| 4 | Trivy first scan (with real examples) | 12 Nov |
| 5 | Automation: weekly scan & Telegram alerts | 14 Nov |
| 6 | Host patching, kernel & Ubuntu Pro | 17 Nov |
| 7 | Watchtower & its three pitfalls | 19 Nov |
| 8 | Routine & staying calm – monthly check & alerts | 21 Nov |
Audience: anyone from “I have a server/PC I manage” upward, no admin experience required. Experienced admins will find a Pro Corner at the end of each part. Use the language switch above for the German version.
Happy following along! Parts that are not yet released appear in the menu on the left as locked (🔒) with their date – everything stays timely and traceable.