Three Auth Bypasses + Two Windows Zero-Days: Tonight's Emergency Window
Three pre-auth bypasses in 48 hours
Three critical authentication bypass vulnerabilities landed inside a 48-hour window, each in infrastructure the enterprise cannot turn off:
| CVE | Product | CVSS | Status | Blast Radius |
|---|---|---|---|---|
| None assigned yet | NGINX rewrite module | ~9.8 | PoC imminent; mass scanning 24-48h | Every edge proxy, ingress controller, API gateway running NGINX |
| CVE-2026-35051 / -39858 | Traefik | 10.0 | Disclosed; patch available | Every downstream service trusting Traefik for auth |
| CVE-2026-4670 | MOVEit Automation | 9.8 | Disclosed; Cl0p affiliates likely tooling | File transfer infrastructure; pattern matches 2023 mass-exploitation campaign |
The NGINX bug is 18 years old, pre-authentication, and affects both NGINX Plus and Open Source. It sat in the rewrite module, which virtually every deployment uses for URL manipulation. The blast radius covers Kubernetes ingress controllers, API gateways, CDN origins, and the appliance long-tail that bundles NGINX quietly.
Why Traefik is the sleeper
The Traefik CVSS 10.0 is functionally an ingress deletion. Services that delegate authentication to Traefik middleware are reachable as if the ingress were not there. It negates the auth layer entirely, not partially. Any architecture where "Traefik handles auth" is the documented control has a zero-day-equivalent exposure today.
MOVEit: Cl0p playbook redux
The last time MOVEit carried a 9.8 auth bypass, the Cl0p campaign compromised hundreds of organizations over months before most victims noticed. The product line's track record is now a documented vendor-risk data point, and Progress Software has not improved the pattern. Cl0p affiliates hunt MOVEit specifically. Assume tooling is being built now.
Compounding: Windows zero-days without patches
In parallel, two unpatched Windows zero-days were disclosed by the same anonymous researcher who previously dropped three Defender bugs: a BitLocker encryption bypass and a CTFMON local privilege escalation. No CVEs, no patches, no Microsoft timeline. The BitLocker bypass is a compliance problem: every SOC 2, HIPAA, and GDPR narrative resting on "data at rest is encrypted via BitLocker" now carries an asterisk.
The four-hour benchmark
PraisonAI CVE-2026-44338 was weaponized four hours after disclosure. That is not a research curiosity. It is the tempo to plan around. PraisonAI sits in the LLM-orchestration layer, where dependency graphs are wide and downstream patch cadence runs in weeks. The MDASH and Mythos evaluations show the same gap from the other direction: for any internet-facing service, the window between disclosure and exploitation now runs in single-digit hours.
Enterprise change-management runs in weeks. The exploitation timeline runs in hours. That gap is the vulnerability, and no single CVE fix closes it.
What to do
Patch or WAF-virtual-patch NGINX tonight; run active discovery beyond CMDB across all public IPs, internal subnets, and cloud accounts
Inventory all Traefik deployments and identify downstream services relying on Traefik for authentication enforcement; patch CVE-2026-35051/39858 immediately
Patch MOVEit Automation to 2025.1.5/2025.0.9/2024.1.8 and begin board-level conversation about product replacement
Deploy compensating controls for Windows BitLocker bypass: enforce TPM+PIN pre-boot auth via GPO, disable sleep/hibernate on high-value endpoints
Scan for PraisonAI deployments across dev, staging, prod, and data-science sandboxes; patch CVE-2026-44338 or take offline immediately