MICROSOFT OFFICE WORD · CVE-2026-113759 · Package
NO FIX YET
Microsoft Word mishandles memory after it is freed, a use-after-free bug. A local attacker with no account can use it to execute code on the machine running Word.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Anyone running an affected version of Microsoft Office Word on a local machine. The sources do not give the affected version ranges or whether a user must open a file to trigger it.
Not affected if unknown
Who cares microsoft-office, windows, word
No fix yet, per the sources.
Use after free in Microsoft Office Word allows an unauthorized attacker to execute code locally.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.