CVE-2025-49695
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 · low confidenceUse after free vulnerability in Microsoft Office enables an unauthorized local attacker to execute arbitrary code by exploiting improper memory management. The vulnerability allows code execution without remote network access, typically through malicious Office documents that trigger the memory corruption condition.
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 versionsall versions= 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/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 versionOpen Word/Excel/PowerPoint, go to File > Account > About [App], or check registry key HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration or HKLM\SOFTWARE\Microsoft\Office\16.0\Common\InstallRoot for version 2016/2019, or HKLM\SOFTWARE\Microsoft\Office\ClickToRun for Microsoft 365/CopilotAffected if The installed version matches Microsoft 365 Apps (any version), Microsoft 365 Copilot (any version), Office 2016, Office 2019, Office LTSC 2021, or Office LTSC 2024
-
Confirm Office application is presentCheck for existence of Office executables such as WINWORD.EXE, EXCEL.EXE, or POWERPNT.EXE in typical locations like C:\Program Files\Microsoft Office\root\Office16 or C:\Program Files (x86)\Microsoft Office\root\Office16Affected if Any of these Office applications are installed on the system
-
Verify Office is processing documentsCheck running processes for WINWORD.EXE, EXCEL.EXE, or POWERPNT.EXE using Task Manager or command: tasklist /FI "IMAGENAME eq WINWORD.EXE"Affected if Office applications are actively running and may be opening documents, as the vulnerability is triggered via specially crafted Office documents
If Microsoft Office (any version from 2016 through 2024, or Microsoft 365/Copilot) is installed on the system, the environment is potentially affected since the use-after-free vulnerability can be exploited when opening specially crafted malicious Office documents.
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 Microsoft security updates for Microsoft Office immediately upon release; until patched, enable Protected View for all Office documents, disable macros, and restrict document sources to minimize exposure.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49695 — 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-49695 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