CVE-2025-27746
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 confidenceUse after free vulnerability in Microsoft Office that allows an unauthorized attacker to execute code locally. This is a memory corruption flaw where the application accesses memory after it has been freed, potentially leading to arbitrary code execution.
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= 2016= 2019= 2021= 2024all versions< 16.0.10417.20003CVSS 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.
-
Check if Microsoft 365 Apps for Enterprise is installedOpen Windows Settings > Apps > Apps & features, or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Select DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like '*Microsoft 365*'}Affected if Microsoft 365 Apps is installed (all versions are affected per the CVE)
-
Check if Microsoft Office 2016 or 2019 is installed and note the exact versionOpen Windows Settings > Apps > Apps & features, or check the Office installation via: Open any Office app > File > Account > About [App] shows the version numberAffected if Installed version equals exactly 2016 or 2019 (specific version match required)
-
Check if Microsoft Office Long Term Servicing Channel 2021 or 2024 is installedOpen Windows Settings > Apps > Apps & features and look for 'Microsoft Office LTSC' entries, or open an Office app > File > Account to view versionAffected if Installed version equals exactly 2021 or 2024 (specific version match required)
-
Check if Microsoft Office Online Server is installedCheck installed programs list for 'Microsoft Office Online Server' or check Programs and FeaturesAffected if Microsoft Office Online Server is present (all versions are affected per the CVE)
-
Check Microsoft SharePoint Server versionOpen SharePoint Central Administration > System Settings > Manage servers in this farm, or run: Get-SPFarm | Select BuildVersion. Also check registry: HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0\Config\VersionAffected if SharePoint Server version is present and less than 16.0.10417.20003
User is affected if they have any Microsoft 365 Apps, Office 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, Office Online Server, or SharePoint Server versions below 16.0.10417.20003 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.10417.20003
Apply Microsoft security updates for CVE-2025-27746 as soon as they become available. Use Protected View for untrusted Office documents and ensure least-privilege user accounts to limit impact.
- Consultation3.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27746 — 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-27746 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