CVE-2025-49711
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 Excel 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 Excel allows an attacker to execute arbitrary code locally. The flaw occurs when Excel improperly handles memory objects, leading to a dangling pointer that can be reused after being freed, potentially enabling 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= 2016= 2019= 2021= 2024< 16.0.10417.20027CVSS 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 Excel application versionOpen Excel, go to File > Account > About Excel (Windows) or Excel > About Microsoft Excel (Mac). Alternatively, check via command line: winword /? or look in Control Panel > Programs and Features > Microsoft OfficeAffected if The version matches one listed as affected by Microsoft for CVE-2025-49711 (note: the affected versions listed use unusual notation; consult Microsoft's official CVE documentation for the complete version list)
-
Identify Office product typeCheck if the installation is Microsoft 365 Apps, Excel 2016, Office 2019, Office LTSC 2021, Office 2024, or Office Online Server. This can be verified in File > Account > About or in Windows Programs and FeaturesAffected if The product is one of: Microsoft 365 Apps (all versions), Excel 2016, Office 2019, Office LTSC 2021, Office 2024, or Office Online Server versions before 16.0.10417.20027
-
For Office Online Server, check server versionIf using Office Online Server, run Get-OfficeWebAppsServer in PowerShell or check the installed version in Programs and FeaturesAffected if The installed version is lower than 16.0.10417.20027
-
Confirm vulnerability trigger conditionThis is a use-after-free flaw in Excel's memory handling that triggers when opening specially crafted Excel files. The vulnerability exists in the Excel application itself, not a specific configuration settingAffected if The Excel application processes files (the flaw is present in the code when handling certain memory objects); no special feature needs to be enabled for the vulnerability to exist in the affected version
A user is affected if they run any version of Microsoft Excel/Office that falls within the affected product and version ranges listed for this CVE.
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.20027
Apply the latest Microsoft Office updates and patches. Ensure Microsoft Office Excel is updated to a version that includes the security fix. Exercise caution when opening Excel files from untrusted sources.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49711 — 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-49711 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