Patch this week:Outlook Zero-Day CVE-2026-124194 Leaks NTLM Hashes. Organizations running Outlook for Windows from Microsoft 365 Apps or Office LTSC 2021 or 2024 on domain-joined machines, especially where NTLM is still accepted and outbound SMB to the internet is open.
Patch this week:Synology DSM: Pre-Auth SQL Injection in the Auth API. Anyone running Synology DSM 7.2.1, 7.2.2, 7.3 or 7.4 below the fixed builds, most urgently where the DSM web interface or rsync is reachable from the internet.
Patch this week:React Server Components RCE: CVE-2026-126187. Teams running React Server Components on a server: Next.js 16.0.0 through 16.4.0 with the App Router, and any app that depends on react-server-dom-webpack, -turbopack or -parcel 19.0.0 through 19.3.0.
Do you run any of these? Cisco BroadWorks, Google Chromium, Microsoft Office, Barracuda Networks Barracuda Email Security Gateway (ESG), Openwave Messaging Limited Webtop Media Transcoder, Barracuda Networks Multiple Products. They are being exploited in the wild (CISA KEV). Patch or mitigate if you do; CISA’s federal deadline is 2026-11-13.
npm: 4 critical advisories (react-server-dom-parcel, react-server-dom-turbopack, react-server-dom-webpack, node-opcua, node-opcua-address-space, node-opcua-server, mongoose, bitcoinjs-lib). Check with npm audit (or: npm ls <package>).
PyPI: 1 critical advisory (gpustack). Check with pip-audit (or: pip show <package>).
None of it touches your stack? Then there is nothing to do today. That is a result, not a failure to read carefully.
Attackers are using this to steal NTLM hashes, but a user has to open a crafted file and the fix arrives through the normal Office update, so deploy it this week and check that outbound SMB is blocked.
Must act: Organizations running Outlook for Windows from Microsoft 365 Apps or Office LTSC 2021 or 2024 on domain-joined machines, especially where NTLM is still accepted and outbound SMB to the internet is open.
Can relax: Users whose Office has already taken the November 10 update. Microsoft's advisory does not list Outlook on the web, Outlook for Mac or the mobile apps.
Install the November 10, 2026 Office security update on every Windows machine with Outlook. It ships through Office update channels, not the Windows cumulative update.
Confirm the build under File > Office Account in Outlook and compare it with the fixed builds for your channel.
Block outbound SMB (TCP 445) from workstations to the internet at the perimeter and on host firewalls.
No exploitation is reported, but this is an unauthenticated flaw in the DSM sign-in path with no workaround, on a product ransomware crews are already targeting, so update now if DSM is reachable from the internet and within days otherwise.
Must act: Anyone running Synology DSM 7.2.1, 7.2.2, 7.3 or 7.4 below the fixed builds, most urgently where the DSM web interface or rsync is reachable from the internet.
Can relax: Devices already on 7.4.1-90080-1, 7.3.2-86009-5, 7.2.2-72806-10 or 7.2.1-69057-13 or later; a NAS reachable only from a trusted LAN or VPN still needs the update but is not an emergency.
Check the installed build in Control Panel > Info Center, or over SSH with cat /etc.defaults/VERSION.
Update in Control Panel > Update & Restore; if the build is not offered yet, download it from Synology's Download Center and install it manually.
Until updated, remove direct internet exposure of the DSM web interface (ports 5000 and 5001 by default) and of rsync; reach the NAS over a VPN instead.
The fix has been on npm since October 14 and the React team says the trigger is extremely rare, so this is a routine but prompt upgrade for anyone running React Server Components, not an emergency.
Must act: Teams running React Server Components on a server: Next.js 16.0.0 through 16.4.0 with the App Router, and any app that depends on react-server-dom-webpack, -turbopack or -parcel 19.0.0 through 19.3.0.
Can relax: Client-only React apps, apps with no framework or bundler that supports Server Components, and anyone already on the fixed React packages or Next.js 16.4.1 or later.
Run npm ls react-server-dom-webpack react-server-dom-turbopack react-server-dom-parcel next and compare the versions with the fixed releases.
On Next.js 16, upgrade to 16.4.1 or later with npm install next@latest, then rebuild and redeploy.
If you depend on the react-server-dom-* packages directly, move to 19.0.9, 19.1.10, 19.2.9 or 19.3.1 on your release line and keep react and react-dom on the matching version.
Openwave Messaging Limited Webtop Media Transcoder Openwave Messaging Limited Webtop Media Transcoder Incorrect Resource Transfer Between Spheres Vulnerability