Patch this week:Visual Studio Copilot CVE-2026-103572: Trailing-Dot RCE. Teams on Visual Studio 2022 17.14 before 17.14.42, Visual Studio 2026 18.10 before 18.10.4, or SSMS with Copilot, especially where agents read untrusted repositories, files or MCP server output.
Patch this week:Windows Shell CVE-2026-96951: Exploited MOTW Bypass. Any organization with Windows 10 or 11 endpoints, or Remote Desktop servers, where people open email attachments, chat files or downloads.
Check exposure:Podman CVE-2026-94603: Images Can Disable the Sandbox. Teams that run images they did not build with rootful Podman (sudo podman run, systemd/Quadlet units as root, CI runners), especially images pulled from public registries or supplied by pull requests.
Most can relax:SlugFest. npm package maintainers who created trusted publisher configurations that never completed a publish, renamed, transferred or deleted a bound repository or GitHub owner, or publish from GitHub Actions issue_comment workflows.
Do you run any of these? Microsoft Windows, Ivanti Connect Secure. They are being exploited in the wild (CISA KEV). Patch or mitigate if you do; CISA’s federal deadline is 2026-10-16.
NuGet: 3 critical advisories (Microsoft.AspNetCore.App.Runtime.linux-arm, Microsoft.AspNetCore.App.Runtime.linux-arm64, Microsoft.AspNetCore.App.Runtime.linux-musl-arm, Microsoft.AspNetCore.App.Runtime.linux-musl-arm64, Microsoft.AspNetCore.App.Runtime.linux-musl-x64, Microsoft.AspNetCore.App.Runtime.linux-x64, Microsoft.AspNetCore.App.Runtime.osx-arm64, Microsoft.AspNetCore.App.Runtime.osx-x64 …). Check with dotnet list package --vulnerable --include-transitive.
None of it touches your stack? Then there is nothing to do today. That is a result, not a failure to read carefully.
Upgrade Connect Secure today and investigate with memory and network forensics, because the Integrity Checker missed this compromise and part of the attack chain still has no fix.
Must act: Every organization running Ivanti Connect Secure 22.8 or 25.1 builds, especially internet-facing VPN gateways.
Can relax: Organizations without Ivanti Connect Secure; per the CVE record, ICS 22.7R2.14 and earlier is not impacted, though it is an older release line.
Upgrade to the fixed Connect Secure release named in Ivanti's advisory (25.1.3.0 per the CVE record)
Do not rely on the Integrity Checker Tool alone; capture memory and network evidence if exposure dates overlap October 1 or later
Hunt welcome.cgi requests whose X-DSCGI-PATH header does not match the URL path
If your developers use Copilot in Visual Studio or SSMS, update this week: exploitation needs only text the agent reads, and the researcher's write-up spells out the chain.
Must act: Teams on Visual Studio 2022 17.14 before 17.14.42, Visual Studio 2026 18.10 before 18.10.4, or SSMS with Copilot, especially where agents read untrusted repositories, files or MCP server output.
Can relax: VS Code users (not in Microsoft's affected list) and installs where Copilot is not used, though updating remains the clean fix.
Update Visual Studio with the Visual Studio Installer to 17.14.42 or 18.10.4 or later, and confirm the version in Help > About.
Update SSMS to the latest 22.x release, since Microsoft's advisory does not name a fixed SSMS build.
Inventory fleet versions with vswhere -all -property catalog_productDisplayVersion.
Roll the October 2026 Windows update out to every desktop this week; attackers are using this to make malicious attachments and downloads skip the warnings that would stop them.
Must act: Any organization with Windows 10 or 11 endpoints, or Remote Desktop servers, where people open email attachments, chat files or downloads.
Can relax: Linux and macOS fleets, and Windows servers nobody logs into interactively, which can follow the normal patch cycle; the attack needs a user to open a crafted file.
Deploy the October 13, 2026 cumulative update to all Windows endpoints this week and reboot.
Verify the OS build on each machine is at or above the fixed build for its version.
Patch users who handle outside files first: finance, HR, support, sales and developers.
If you run third-party images with rootful Podman, upgrade to 5.8.8 or 6.1.3 now, because an image can switch off the sandbox you asked for; rootless Podman and trusted-image-only hosts can patch on a normal cycle.
Must act: Teams that run images they did not build with rootful Podman (sudo podman run, systemd/Quadlet units as root, CI runners), especially images pulled from public registries or supplied by pull requests.
Can relax: Rootless Podman users, since checkpoint/restore is not supported rootless, and hosts that only run vetted images from registries you control.
Check versions on every host and runner: podman --version and sudo podman --version.
Upgrade to Podman 5.8.8 or 6.1.3, or your distribution's patched package (dnf update podman / apt-get install --only-upgrade podman), once available.
Until patched, do not run untrusted images with rootful Podman; use rootless Podman for third-party images.
The hole was closed on npm's side on October 2, 2026 and no abuse has been reported, so most teams have nothing to patch; maintainers should still spend five minutes auditing trusted publisher bindings and recent publishes.
Must act: npm package maintainers who created trusted publisher configurations that never completed a publish, renamed, transferred or deleted a bound repository or GitHub owner, or publish from GitHub Actions issue_comment workflows.
Can relax: Package consumers and maintainers whose trusted publisher bindings have already published successfully from a repository they still control; npm binds those to the repository's immutable identity.
Run npm trust list <package> (npm 11.15.0 or later) for each package you maintain and confirm every bound repository slug still belongs to you.
Delete and re-create bindings after any repository or owner rename, transfer or deletion; remove a binding before deleting its repository.
Publish once from a newly created binding within 48 hours so it is validated against the repository's immutable identity, or it will expire.