CVE-2025-27747
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 Word 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 Word allows an attacker to execute code locally by continuing to reference memory after it has been freed. This memory corruption can be triggered by a specially crafted Word document.
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= 2019= 2021= 2024= 2016= 2019= 2016CVSS 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.
-
Verify Microsoft Word installationOpen Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed Office products. Look for Microsoft Word or Microsoft Office entries.Affected if Microsoft Word, Microsoft Office, or Microsoft 365 Apps is installed and the version matches the affected ranges listed in the CVE (Microsoft 365 Apps all versions, Office 2019, Office LTSC 2021/2024, Word 2016).
-
Confirm the exact Word version numberOpen Word, go to File > Account > About Word, or check the version via command line using 'winword /?' or in Excel with '=VERSION()' function if available. Record the full version number (e.g., 16.0.xxxxx.xxxx).Affected if The installed version falls within the affected version ranges (Microsoft 365 Apps - all versions, Office 2019, Office LTSC 2021/2024, Word 2016, SharePoint Server 2016/2019 when Word documents are processed).
-
Check Windows Update for CVE-2025-27747 patchOpen Settings > Update & Security > Windows Update > View update history, or check Microsoft Update Catalog online for security update KB56083 (or similar CVE-referenced update).Affected if The CVE-2025-27747 security update has NOT been installed - the system remains vulnerable.
-
Determine if SharePoint Server is processing Word documentsFor SharePoint environments, verify if the server runs SharePoint Server 2016 or 2019 and accepts Word document uploads. Check SharePoint Central Administration for installed version.Affected if SharePoint Server 2016 or 2019 is installed and processes untrusted Word documents without the security update applied.
If Microsoft Word, Microsoft Office, or Microsoft 365 Apps is installed and the CVE-2025-27747 security update has not been applied, the environment is affected by this use-after-free vulnerability.
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 dataApply the Microsoft security update for CVE-2025-27747 once released; until then, restrict opening untrusted Word documents and ensure up-to-date antivirus protection is active.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27747 — 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-27747 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