Last Tuesday, Microsoft released fixes for 1,259 security flaws. It was the second month in a row above 1,000, and Microsoft has now fixed more than 5,100 flaws this year. The updates cover Windows, Office, SQL Server, and SharePoint Server, which is much of what runs a typical manufacturer.Microsoft Just Patched 1,259 Flaws Again. Here Is How a Manufacturer Decides What to Patch First

Nobody can treat 1,259 fixes as equally urgent. The skill is knowing what to do first.

The One Flaw Already Being Exploited

Of all those fixes, Microsoft flagged one as actively exploited. It affects Outlook, and Microsoft rated it only Moderate. An attacker sends a specially crafted message file and persuades someone to open it. Outlook then connects to a location the attacker controls without showing the usual external content warning. That can leak a Windows sign-in credential, called an NTLMv2 hash, which can be used to impersonate the person who opened the file.

One security researcher said the Moderate label undersells it: it takes a single click, it hits software nearly every company runs, and a stolen credential can open doors well beyond the inbox. CISA added it to its list of known exploited vulnerabilities, with a federal deadline of November 24.

A Patching Order That Works

Security experts’ advice this month comes down to three steps:

  1. Internet-facing systems first. Firewalls, VPNs, remote access, and anything an outsider can reach.
  2. Anything already being exploited second. The Outlook flaw belongs here, and CISA’s known exploited list is the quickest way to spot these.
  3. Everything else on a regular schedule. Before you panic, check whether you even use the affected component.

The Manufacturing Catch

Many plants delay Windows updates because they fear breaking an ERP, MES, or CAD system. That caution is reasonable, but skipping updates is not the answer. The answer is testing. Patch a non-critical machine first, confirm your key applications still run, then roll out in stages. Exploited flaws like this month’s Outlook bug should not wait for the next maintenance window.

What Your Team Should Do Right Now

  • Install the November Windows and Office updates, starting with machines that run Outlook.
  • Remind your team not to open unexpected message files or attachments, even from familiar names.
  • Ask IT to confirm the firewall blocks outbound file-sharing traffic to the internet, which limits this kind of credential leak.
  • Have IT keep a short list of systems that need patch testing, such as ERP, MES, and CAD workstations, so testing happens fast instead of not at all.
  • Confirm someone owns patching every month and verifies it finished.

The Bottom Line

Patch volume keeps growing, and no team can chase every fix. Patch what is exposed first, then what is exploited, and test the rest on a schedule so production stays up.

Have questions about patching around your ERP and shop floor systems? Reach out to us. We are here to help.