Skip to content
Lacambra Web Portal Services
← 2026, week by week
Security · Week 5, 26 January to 1 February 2026

CVE-2026-21509: the Office fix that needed a restart

Microsoft rushed out a fix for an Office flaw already used in attacks. Newer Office needed a restart to be safe, and Office 2016 and 2019 needed more.

A short stack of plain cream paper on a dark desk, a small steel fishhook resting on the top sheet and an oxblood paperweight beside it.

On 26 January Microsoft released an emergency fix for CVE-2026-21509, a flaw in Office that was already being used in attacks. It let a crafted Office file get past the safeguards that stop documents from using vulnerable embedded controls, and all an attacker needed was for someone to open the file. Microsoft 365 and Office 2021 and later were protected by a change on Microsoft's side, but only once each Office application had been restarted. Office 2016 and 2019, whose support had ended on 14 October 2025, needed a registry change until their own security update was installed.

The fix came outside Microsoft's monthly update cycle, and CISA added the flaw to its catalogue of exploited vulnerabilities the same day. At first the updates for Office 2016 and 2019 were not ready, The Register reported, and Microsoft pointed those customers to the registry change, which BleepingComputer set out step by step. By 28 January Microsoft was telling reporters the updates were out, though its own pages, including the support article for Office 2016, date them 26 January.

What was exploited, and how fast

Microsoft did not say who was behind the attacks. Ukraine's CERT-UA filled part of the gap. Three days after Microsoft's alert it found Word documents exploiting the flaw, one of them created the day after the fix, and emails posing as Ukraine's hydrometeorological centre went to more than 60 government-related addresses, BleepingComputer reported. CERT-UA attributed the campaign to APT28, a group associated with Russia's military intelligence, and further investigation found three more documents it had used against organisations in the EU.

The lesson in that timeline is the gap. A fix published on a Monday had attackers building documents by Tuesday and sending them by Thursday, which leaves an office days, not weeks, to have it in place.

Why the restart and the version number mattered

For most offices the fix arrived on its own and then waited. A change on Microsoft's side protects Office 2021 and later only after each application restarts, so a copy of Outlook that nobody has closed since the fix is not protected by it. It is the cheapest step in the whole response, and the easiest to assume has happened.

The older versions carry the larger lesson. Office 2016 and 2019 reached end of support in October 2025, and under Microsoft's policy end of support means no new security updates. Microsoft shipped one anyway this time, but the registry change and the separate update fell on the offices still running those versions, and CISA's catalogue entry advises moving off products that are out of support.

What it means for the documents in your systems

The attack needed one thing from its victim: opening a file that came from outside. Many of an office's documents need not arrive that way. The systems I build produce Word and Excel output to an office's exact templates from the records already in them: the briefing books, letters and reports it sends out. A process that runs in one system, rather than through a chain of spreadsheets and email threads, sends far fewer files around. Every request, approval or letter that comes out of a system instead of an inbox is one fewer attachment that staff have learned to open without thinking.

Five checks for your copies of Office

  • Find out which version of Office each computer runs: in Word, File, then Account, then About. Office 2016 should show build 16.0.5539.1001 or later, and Office 2019 build 16.0.10417.20095 or later.
  • After an emergency fix, have everyone close and reopen their Office applications, and check that they did.
  • Plan the move off Office 2016 and 2019. Their support has ended, and the next fix may not come.
  • Leave Protected View on, and treat Enable Editing on a file from outside as a decision, not a habit.
  • Move routine requests and approvals into a system, so that fewer documents arrive as attachments.

If your office still runs on attachments passed from inbox to inbox, the fit check will tell you whether a system would be worth building.

Sources

  1. Microsoft Security Response Center, Microsoft Office Security Feature Bypass Vulnerability, 26 January 2026
  2. Microsoft Support, Description of the security update for Office 2016: January 26, 2026 (KB5002713), 26 January 2026
  3. BleepingComputer, Microsoft patches actively exploited Office zero-day vulnerability, 26 January 2026
  4. The Register, Office zero-day exploited in the wild forces Microsoft OOB patch, 27 January 2026
  5. BleepingComputer, Russian hackers exploit recently patched Microsoft Office bug in attacks, 2 February 2026
  6. Microsoft Learn, Ending Support in 2025
  7. Cybersecurity and Infrastructure Security Agency, CISA Catalog of Known Exploited Vulnerabilities

Enrique Lacambra III builds internal business systems from Cainta, Rizal.

Email me← All writing

Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.