Monthly Fallout Report

October 2025 Fallout

172 vulnerabilities, 3 actively exploited zero-days, Windows 10's final free update, and a bug that killed localhost for every developer on Windows 11.

Damage Rating
172
Vulnerabilities
3
Zero-Days
8
Critical RCEs
2
KB Updates

Fallout Timeline

Initial Release — Patch Tuesday Day 0

Vault dwellers, October 2025 is a historic month for two reasons: 172 vulnerabilities — the highest count of the year — and the official end of free Windows 10 security updates. RIP, old friend. On the zero-day front, three are being actively exploited in the wild and all three hit CISA's Known Exploited Vulnerabilities catalog. CVE-2025-24990 lives in the legacy Agere Modem driver (ltmdm64.sys) that shipped with every version of Windows, including Server 2025 — Microsoft's fix is to delete the driver entirely, which will break fax modems. CVE-2025-59230 is the first-ever RasMan (Remote Access Connection Manager) zero-day exploited in the wild — it's been patched 20+ times since 2022 but never as a zero-day until now. CrowdStrike linked active exploitation to at least one threat actor. CVE-2025-47827 is a Secure Boot bypass in IGEL OS (thin clients common in healthcare and retail), weaponized with a public PoC from June 2025. Critical highlights: CVE-2025-59287 is a CVSS 9.8 WSUS RCE allowing unauthenticated attackers to execute code against your update server — your update infrastructure itself. Post-October update, CISA confirmed CVE-2025-59287 was also exploited in the wild. including 2 publicly disclosed zero-days and 9 criticals. The headliner is CVE-2025-55234 — a privilege escalation flaw in Windows SMB Server that enables relay attacks, allowing attackers to impersonate users and escalate privileges. No active exploitation confirmed, but public details are out there, so the clock is ticking. The second zero-day is CVE-2024-21907 — a year-old denial-of-service flaw in Newtonsoft.Json now bundled into SQL Server patches (yes, really — a 2024 CVE finally getting its Microsoft fix in 2025). Critical NTLM flaw CVE-2025-54918 (CVSS 8.8) is flagged as "Exploitation More Likely" — chain it with other bugs and attackers could reach SYSTEM. Office RCE via CVE-2025-54910 is trigged through the Outlook Preview Pane with no user interaction — treat that one as urgent. Windows 10 (KB5065429) and Windows 11 (KB5065426/KB5065431) are this month's deployments. September also fixes the NDI streaming chaos left behind by August's updates. Patch fast, but hold developer machines — there's a big one incoming.

CVE-2025-24990 CVSS 7.8 ⚠️ Exploited in Wild

Windows Agere Modem Driver EoP — shipped on every Windows system since forever. No modem needed for exploitation. Microsoft's fix: delete the driver entirely. Fax modem users, you've had a good run.

CVE-2025-59230 CVSS 7.8 ⚠️ Exploited in Wild

Windows RasMan (Remote Access/VPN) EoP to SYSTEM — first-ever RasMan zero-day after 20+ patches for the service since 2022. CrowdStrike confirmed active threat actor exploitation. All supported Windows/Server versions affected.

CVE-2025-47827 CVSS 4.6 ⚠️ Exploited in Wild

Secure Boot bypass in IGEL OS (thin clients). Public PoC since June 2025 — attackers can deploy kernel-level rootkits and steal VDI credentials. Physical access typically required (evil maid attack).

CVE-2025-59287 CVSS 9.8

WSUS RCE — unauthenticated attacker can compromise your Windows Server Update Service via crafted event deserialization. Your patching infrastructure becomes the attack vector. Marked "Exploitation More Likely," then confirmed exploited post-release.

CVE-2025-55682 CVSS 6.8

BitLocker Security Feature Bypass — physical access enables bypass of encryption protections. Low complexity, relevant for unattended or physically accessible devices.

Sources: BleepingComputer · Rapid7 · CrowdStrike · Tenable

72 Hours Out +3 Days Issues Active

Within hours of KB5066835 rolling out, developers across Windows 11 24H2 and 25H2 discovered that localhost (127.0.0.1) was completely broken. Browser connections returned ERR_HTTP2_PROTOCOL_ERROR or ERR_CONNECTION_RESET. Visual Studio couldn't attach to IIS Express. The Duo Desktop authentication app stopped working. Autodesk Vault users couldn't connect to local servers. Root cause: a regression in HTTP.sys (the kernel-mode HTTP driver) that terminates HTTP/2 sessions on the loopback interface during handshake. A secondary regression broke WinRE — keyboards and mice stopped working in the Windows Recovery Environment, meaning if you needed to recover a broken PC, your input devices wouldn't work. Microsoft acknowledged the HTTP.sys issue on October 17 and deployed a Known Issue Rollback (KIR). Registry workaround: add EnableHttp2Tls and EnableHttp2Cleartext = 0 under HKLM\System\CurrentControlSet\Services\HTTP\Parameters.

Sources: BleepingComputer · Windows Latest · Windows Forum

2 Weeks Out +14 Days Largely Resolved

Microsoft's KIR (Known Issue Rollback) propagated to consumer devices via Windows Update silently — many users found it fixed on reboot without a manual update. Enterprise admins needed to deploy a specific Group Policy KIR package. The WSUS RCE (CVE-2025-59287) was confirmed exploited in the wild by October 24, Microsoft issued an out-of-band update with a more comprehensive fix. WinRE keyboard/mouse fix arrived via a separate OOB update (KB5070773). Windows 10 end-of-support left a long tail: organizations discovering devices not enrolled in ESU, facing a hard choice between paying Microsoft for extended support or facing zero future patches.

Sources: BleepingComputer · Tenable · AskWoody

Resources