Four Unauthenticated Criticals — Patch Two, Assume Compromise on a Third
The through-line this cycle is not any single flaw but timing: attackers are harvesting slow patchers on n-days while a nine-year-old kernel race sits below every Linux control you trust.
The shared mechanism across these criticals is authentication bypass or its equivalent: no credentials, no user interaction, no malware to detect. That is the pattern detection engineering should key on. It splits into two tracks. Flaws to patch on a same-week clock, and one that changes forensic assumptions entirely.
The patch-now track
Check Point CVE-2026-16232 is the priority. The auth bypass grants full admin over Security Management and Multi-Domain servers. Exploitation is confirmed. A handful of customers have already been notified of compromise. The CISA remediation deadline is July 25 — Saturday. Apply the jumbo hotfix for R81.20/R82/R82.10, restrict Trusted Clients, and treat the management plane as potentially already touched. Review admin-action logs for the pre-patch window, not just patch status.
FreePBX (GHSA-37j8-fhxx-9vhp, CVSS v4 9.3) is unauthenticated RCE via the UCP Node server on ports 8001/8003. Attackers inject Asterisk Manager Interface actions to run commands as the asterisk user. A second SQL-injection path via crafted SIP Caller ID headers can rewrite admin credentials outright. Patch to UCP 17.0.9 and modules 16.0.11/17.0.6. Until then, firewall 8001/8003 externally and filter SIP 'From' header content.
Two more belong in this cycle. Windmill CVE-2026-29059 — an unauthenticated path traversal leaking the SUPERADMIN_SECRET token — was patched in January and only came under attack afterward. Rotate the secret and review for pre-patch admin abuse. Windows Event Logging RCE (CVE-2026-50502) lands in the current patch cycle.
The assume-compromise track: RefluXFS
RefluXFS (CVE-2026-64600) breaks the forensic model. It is a race condition in XFS reflink handling triggered by concurrent O_DIRECT writes, corrupting on-disk blocks directly. A filesystem-allocation bug, not a memory-safety one. That placement matters. It sits below KASLR, SMEP, SMAP, SELinux enforcing, seccomp and container isolation, grants passwordless root, survives reboot, and leaves zero kernel logs. The vulnerable path has existed since kernel v4.11 in 2017, exposing an estimated 16.4M systems on RHEL, Oracle Linux, Amazon Linux and Fedora running the default reflink=1.
Sources diverge on remediation readiness. Cyberpresso reports vendor kernels are already available for RHEL, Oracle, AlmaLinux, Rocky and Fedora. TLDR InfoSec describes the vendor fix as still pending. Resolve that against the relevant distro advisories before assuming a patch exists. Either way, there is no live-patch workaround. Patching requires a reboot. Because kernel logs stay silent, file-integrity monitoring on SUID-root binaries and /etc/passwd is the only detection path.
The smart move
Run the two tracks in parallel. Same-week patching for Check Point, FreePBX, Windmill and the Windows fix. A prioritized RefluXFS reboot campaign on internet-facing, multi-tenant and CI-runner Linux, where an unprivileged local foothold most easily meets untrusted users. RefluXFS is the silent escalation partner for any initial access, including a compromised webmail box. Treat it as the second half of every foothold you find.
What to do
Apply the Check Point jumbo hotfix (R81.20/R82/R82.10) and restrict Trusted Clients on all Security Management/Multi-Domain hosts before the July 25 CISA deadline, then review management-plane logs for pre-patch admin abuse.
Patch FreePBX to UCP 17.0.9 (modules 16.0.11/17.0.6), firewall ports 8001/8003, and launch a RefluXFS kernel-patch-and-reboot campaign on internet-facing, multi-tenant and CI-runner Linux.
Rotate any exposed Windmill SUPERADMIN_SECRET and add file-integrity monitoring on SUID-root binaries and /etc/passwd as the RefluXFS detection path, since kernel logs stay silent.