Microsoft Patch Tuesday – October 2025

[#1]

October Patch Tuesday lands with 173 fixes, including 9 critical and 3 actively exploited.

Highlights:

• Agere Modem Driver EoP (CVE-2025-24990) – driver removed after active exploitation
• RasMan EoP (CVE-2025-59230) – local attackers can gain SYSTEM
• Secure Boot bypass (CVE-2025-47827) – IGEL OS flaw exploited to load unsigned code

Full breakdown and the October audit to find outdated devices 👇

• Microsoft Patch Tuesday – October 2025 - Lansweeper

[OT-Guy]

Thank you for providing user-friendly access to the Patch Tuesday files.  Exactly what I was hoping for!

[darrenkimber]

Will LS release an update for the newly released CUs Microsoft release late last week? Thanks

[dcm-ebb]

+1 for adding something or at least a suggestion for how to catch the OOB updates for those of us who barely even have time to do the restarts...

[dcm-ebb]

I went in and found around about line 150 where OSname='Win 2016' And Subquery2.Buildnumber < 8519 and change this to 8524 which is build for the server I have patched.

Went in and found around about line 170 where OSname='Win 2019' And Subquery2.Buildnumber < 7919 and change this to 7922 which is build number for server I have patched.

Neither of these changes makes the report change the status for any of the other servers, so I think I am missing some steps.

[dcm-ebb]

ok, I am nitpicking by this point. by making these changes I can get the report to show me which builds have the lower build number and what patch needs installed to bring to the latest build number, and then it is still true to the report anyway that the rest are patched up to the monthly update. I then just open the 2016 in one report and the 2019 in another instance and can see what remains to be patched.

around line 150:

tsysOS.OSname = 'Win 2016') And SubQuery2.Buildnumber < 8524
Then 'KB5070882'

around line 170:

tsysOS.OSname = 'Win 2019' And SubQuery2.Buildnumber < 7922 Then
'KB5070883'

[nwraorion]

I have a system that the report flags as needing KB5070773, however it is running Win 11 25H2 2025-10 - build 26200.6899 and appears to be fully up to date.  Can this get fixed?