CVE-2025-59227
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUse after free in Microsoft Office allows an unauthorized attacker to execute code locally.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA use-after-free vulnerability in Microsoft Office allows an attacker to execute code locally by manipulating memory after a pointer has been freed, leading to arbitrary code execution in the context of the current user.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versions< 16.0.19328.20000= 2016= 2019= 2021= 2024CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Microsoft Office productsOpen any Office application (Word, Excel, PowerPoint), go to File > Account > About [App] to see the version number. Alternatively, run 'winword --version' or 'excel --version' from Command Prompt to retrieve version information.Affected if Any Microsoft 365 Apps, Office 2016, Office 2019, Office LTSC 2021, or Office LTSC 2024 is installed.
-
Check Microsoft 365 Copilot versionOpen Microsoft Word or Excel, click the Copilot icon or go to Home tab to find Copilot version. Alternatively, check the installed Office version number in File > Account > About and look for version numbers lower than 16.0.19328.20000.Affected if Microsoft 365 Copilot is present with version lower than 16.0.19328.20000.
-
Verify Office 2016 installationCheck Program Files or Program Files (x86) for Microsoft Office\Office16 folder. In Control Panel > Programs > Programs and Features, look for 'Microsoft Office 2016' in the installed programs list.Affected if Microsoft Office 2016 is installed (any version number).
-
Verify Office 2019 installationCheck Program Files or Program Files (x86) for Microsoft Office\Office16 folder with 2019 license files. In Control Panel > Programs > Programs and Features, look for 'Microsoft Office 2019' in the installed programs list.Affected if Microsoft Office 2019 is installed (any version number).
-
Verify Office Long Term Servicing Channel installationIn Control Panel > Programs > Programs and Features, look for 'Microsoft Office Long Term Servicing Channel 2021' or 'Microsoft Office Long Term Servicing Channel 2024' in the installed programs list. These typically appear with LTSC designation.Affected if Microsoft Office LTSC 2021 or Microsoft Office LTSC 2024 is installed.
Your environment is affected if Microsoft 365 Apps (any version), Microsoft 365 Copilot (version < 16.0.19328.20000), Office 2016, Office 2019, Office LTSC 2021, or Office LTSC 2024 is installed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data16.0.19328.20000
Apply Microsoft security updates for Microsoft Office when available, and ensure Office applications are kept current through standard patch management processes.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59227 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59227 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data