CVE-2025-59221Patch(microsoft / 365_apps)

LOWCVSS 7.0 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch microsoft 365_apps systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

Use after free in Microsoft Office Word allows an unauthorized attacker to execute code locally.

1.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-416

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • 365_apps
  • office
  • office_long_term_servicing_channel
  • sharepoint_server

Threat summary

  • Patch or workaround signal is available
  • 1 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 1 signal
  • 1 total mentions across 1 day

Affected systems

Vendors
Products
365_appsofficeoffice_long_term_servicing_channelsharepoint_serverword

5 versions affected across 5 products

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-09-11: 1Patch / Workaround · 2026-09-11: 109-11
Signal classification1 categories
Patch
1100.0%
Full discourse1 post
  • Haifei Li@HaifeiLi
    Patch

    Two recent weird/wild cases related to MSRC. 😐 1. One bug was processed for 5 months, reported on April 2nd, got the only update in early Sep, that's a "low severity" decision (means no CVE no bulletin etc), but at the same time I was told they're going to patch that "low severity" bug on Sep. Patch Tuesday (should already patched now). I'll probably do a write-up because if I don't say the bug doesn't even exist. 2. Another bug, which in technical, is actually the same bug I reported last year. Last year they acknowledged the bug and issued the patch (October, CVE-2025-59221). In May I found the bug somehow was still there - a failed patch, not sure what happened - hard to trace all the Office stuff! Anyway, I reported it to them again. Wild enough, I just learned that this time they've closed the case, the reason is that they couldn't reproduce the bug.. for a bug supposes to have been patched.. And nobody bother to ask me back for help but close that straightly?

    Post summary

    The article centers on Microsoft’s patching schedule for a low‑severity bug and a second bug that was ultimately closed after failed reproduction, highlighting patch details and possible debunking.

    0002432.1K
    8.9K followersView on X
CPE platform detail14 entries

14 of 14 entries

PartVendorProductVersionTarget SWTarget HW
Appmicrosoft365_apps--x64
Appmicrosoft365_apps--x86
Appmicrosoftoffice2019-x64
Appmicrosoftoffice2019-x86
Appmicrosoftoffice_long_term_servicing_channel2021-x64
Appmicrosoftoffice_long_term_servicing_channel2021-x86
Appmicrosoftoffice_long_term_servicing_channel2021macos-
Appmicrosoftoffice_long_term_servicing_channel2024-x64
Appmicrosoftoffice_long_term_servicing_channel2024-x86
Appmicrosoftoffice_long_term_servicing_channel2024macos-
Appmicrosoftsharepoint_server2016--
Appmicrosoftsharepoint_server2019--
Appmicrosoftword2016-x64
Appmicrosoftword2016-x86

Explore more