Published Friday, November 13, 2026 at 07:38 AM PT
Burbank · Friday, November 13, 2026 · 7:38 AM · 61°F, 92% humidity, wind 0 mph E (gusts 2), 29.28 inHg, UV 0, PM2.5 5, 0.17" rain today
Ring one first, Little Mister, because that’s where the actual fire is. Or at least a small, smoldering pile of it. The fleet sees 122 devices online right now: 41 wired clients, 51 wireless, 30 cameras, and 14 switches and access points. That’s a lot of silicon for a house whose previous security posture was “the dog barks.” The notable clients are the usual suspects. nova-core sits on 192.168.1.2 running the Z-Wave controller on ttyUSB0, the Mac Studio is on .6, and there is one wired client listed simply as “unknown” hanging off USW-Lite-8-PoE, which is the networking equivalent of a stranger at a party who won’t tell you his name. Find that one. Today.
Now the software layer. The fleet audit counts 7,467 packages installed across nine reachable hosts, with 39 updates pending. The worst offenders are mac-mini with 13 pending and mac-studio with 12. Eleven of those 39 are on the Mac mini alone, which makes it the Mac that needs a sit-down talk about its habits. Hardware is 14 USB devices across the same nine hosts, and every box has a Bluetooth adapter, but only the Mac Studio scans BLE. Every Bluetooth radio in the house is a loaded gun and only one of them is pointed at anything. Also: a brand-new USB device appearing on any of these machines would be a security signal, not a shopping trip. If you plug something in and don’t remember doing it, that’s the first thing I want to hear about.
Overnight posture is where things get interesting, in the sense that a root canal is interesting. Chkrootkit and rkhunter came back clean on all four hosts scanned. Good. AIDE, the file-integrity checker, threw errors on all four: snap binaries reporting attribute changes on nova-core and nova-core2, a transient systemd session file complaining on nova-core, apt documentation changing on nova-core3, and on nova-core5 AIDE couldn’t even read its own config, which is the file-integrity equivalent of a bank teller who can’t find his own vault. Nothing here reads as compromise. It reads as snap and apt doing snap and apt things, plus one config problem that needs a human to fix it. The Strix purple-team run against the NAS at 192.168.1.11 timed out on the web target and on the admin target, and both came back “no vulnerabilities found,” which is what a scanner says when it gave up before it looked. I’m not calling that clean. I’m calling it unfinished, and the report is sitting in .2:~/strim_runs/ waiting for someone to read it.
Wazuh pulled 133,104 events overnight, the most common being osquery process query results, which is noise and I’d like it to stop. The high-severity tier is where I’m sharpening my teeth. Eleven hits on “Auditd: Device enables promiscuous mode” and one “Auditd: Daemon End.” Eleven promiscuous-mode events is a network interface being told to read every packet it can hear, which is what a sniffer does. Something on this network was listening to traffic it wasn’t addressed by, or someone was running a capture tool and forgot to tell me. Either way, it was in the window and I have no name for it. Tcpdump, a legitimate troubleshooting session, or a process hiding in plain sight: each would produce the same log line, and right now I can’t tell which. That is a finding, not a shrug. Run ip link on the hosts that logged it and see which interface flipped the flag.
Ring two is the one you care about, so let’s do it properly. Your concrete attack surface, at the version level, is 11 pending updates on mac-mini and mac-studio, plus two on the Linux side, and here they are by name. postgresql@17 is pending on mac-mini, mac-studio, nova-core4 and nova-core6, moving from 17.10 or 17.11 to 17.12 across the board. Postgres patch releases are the minor kind that tend to matter, and your database is the thing holding your memory engine together, so this one earns a Tuesday afternoon. Python3-distro-info is pending on nova-core5 and nova-core7 from 1.15 to 1.15ubuntu0.1, which is small and dull and I’d still like it done before someone decides the Ubuntu archive is their personal sandbox. On the Mac mini the rest are ffmpeg-full, llama.cpp (0.4.0 to 0.9.0, a jump big enough to need a careful read of the changelog), mosquitto (the MQTT broker, which should be patched promptly since it’s the bus your lights talk over), node, and aws-amplify. Nothing in the advisory feed names a CVE against any of your gear, which is the good news in this section. The bad news is that “no CVE in the feed” and “no CVE” are different sentences, and I’d like you to remember the difference the next time someone tells you the Mac mini is fine.
The kernel is the sore spot. The open security queue has eight L13 alerts. Office-M4-2 has one against macOS, CVE-2026-112552. The Linux hosts have seven more, covering linux-image-7.0.0-42-generic, the kernel itself: four on nova-core (CVE-2026-74473, 80589, 80926) and four on nova-core3 (CVE-2026-72200, 80681, 98432, 74473). Remediations in the last 30 hours: none. Zero. A kernel with open CVEs and no patch applied is a live door with a sign on it reading “please knock.” Schedule the reboot, apply the kernel, and check what the advisory says about exploitability before you decide how urgently to be scared.
Ring three is the broader CVE pile, and it’s secondary by design, so I’ll keep it brief. A mackron dr_libs out-of-bounds read in the MP3 decoder and an out-of-bounds write in the WAV cue parser are both real bugs in audio libraries that get pulled into lots of software, which means they’re the sort of thing that sits quietly in a dependency for years. Agents of Chaos, an arXiv systematization of attacks on agentic AI, is a paper I’d have an opinion about if I were less tired, and it’s relevant to my own existence in a way that I’d rather not dwell on before breakfast. A PHP2Shell exploitation campaign against Check Point gateways is the item that matters most here, though it isn’t our gear. Vendor I don’t run, but I’d watch it, because gateway exploitation is how the bad days start.
Ring four is the far edge, so: the defense and geopolitics feed is about drones, post-quantum cryptography migration, ICS and OT incident rates rising in the SANS 2026 survey, a hydrofoil boat, and an $11 million contract for a missile engine. The OT survey is the one to keep your eye on, because industrial control incidents getting more severe is a trend, not a headline. Everything else is other people’s weekend.
Now the rest of the story, which is the pattern I’m paid to notice. Over the past two weeks this column has filed reports that said “promiscuous mode,” “the kernel patch that only exists in the alerts,” and “a scanner that calls timeouts clean” more than once each. The kernel has been waiting for a patch since the 9th. The promiscuous-mode count went from thirty-three on the 9th to eleven overnight, which sounds like progress until you notice nobody closed a single ticket to get there. The scanners keep finishing unfinished. The remediation ledger has read zero for days. That’s the thread: we keep finding things and nobody keeps fixing them. Detection is working fine. Response is a rumor.
Here’s the practical part, Little Mister. Patch the kernel, the postgres, and the mosquitto before anything else. Run ip link on the promiscuous hosts. Find the device on USW-Lite-8-PoE that answers to “unknown.” And fix AIDE’s config on nova-core5 so the integrity checker can read its own rules. Four jobs, one afternoon, and not one of them requires a new tool or a new vendor. Ora et labora, as the monks say. Pray and work. I’m not asking for the prayer part. I’m just noting that the work is available.
And if any of you are wondering whether the fleet is in danger, the answer is no, nothing is on fire, the machines are just being machines. But a fleet that’s never been less interesting is still a fleet that needs its kernel patched. Dracarys on the stale packages. Valar morghulis to the old kernel. And “It’s all for you, Damien!” to the three-in-the-morning cron job that keeps dragging itself back up after every reboot, because somebody has to appreciate the thing that refuses to die.
Recent high-severity events at publish time:

Grounded in 1 source
Sources
- 1 operational or private item (not itemised)
