dbcve.org
365 AppsApplication · Microsoft

CVE-2025-49697

HIGH · 8.4 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 16.0.10417.20027 or later.
See remediation →
89/100
Remediation priority · High
No privileges Zero-click

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 · unedited
Heap-based buffer overflow 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 confidence

A heap-based buffer overflow vulnerability exists in Microsoft Office that allows an unauthorized local attacker to execute arbitrary code. The vulnerability stems from improper memory handling when processing Office documents, potentially enabling an attacker to overflow heap allocations and inject malicious code.

MitigationApply Microsoft security updates for Microsoft Office as soon as they become available. Until a patch is released, exercise caution with untrusted Office documents and consider enabling protected view or macros disabled by default.

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 data
365 AppsApplication
Affected:all versions
365 CopilotApplication
Affected:all versions
OfficeApplication
Affected:= 2016= 2019
Office Long Term Servicing ChannelApplication
Affected:= 2021= 2024
Office Online ServerApplication
Affected:< 16.0.10417.20027

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Microsoft Office is installed
    Open a command prompt and run: regquery "HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" /v VersionToReport 2>nul. For legacy installs, check: regquery "HKLM\SOFTWARE\Microsoft\Office\16.0\Common\InstallRoot" /v Version 2>nul
    Affected if No Office installation found means not applicable
  2. Determine the installed Office version
    Open any Office app (Word, Excel), go to File > Account > About [App]. Alternatively, run: winword.exe /? | findstr "Version" from Command Prompt
    Affected if Version displayed matches any of the affected versions (2016, 2019, 2021, 2024, or any M365/365 Copilot version)
  3. Check Microsoft 365 Apps version
    Open any Office app, go to File > Account. Look for "Update Options" > "View Updates" to see the current channel and version. Or run: msiexec /x {GUID} /qn /l*v %temp%\office_version.log and check the log
    Affected if Any Microsoft 365 Apps version is installed (all versions affected)
  4. Check Microsoft Office Online Server version
    On the server, open SharePoint Management Shell and run: (Get-SPOWebTemplate -CompatibilityLevel 15 | Where-Object {$_.Title -like "*Office*"}). For version: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office Web Server\16.0\WSS' | Select-Object Version
    Affected if Office Online Server version is below 16.0.10417.20027

If any version of Microsoft Office, Microsoft 365 Apps, Microsoft 365 Copilot, or Office Online Server below 16.0.10417.20027 is installed and the user opens a specially crafted malicious Office document, the environment is affected by this heap-based buffer overflow vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 16.0.10417.20027 or later
Fixed in 16.0.10417.20027
Interim mitigation

Apply Microsoft security updates for Microsoft Office as soon as they become available. Until a patch is released, exercise caution with untrusted Office documents and consider enabling protected view or macros disabled by default.

Recommended fix High confidence

Office Online Server: 16.0.10417.20027 or later; Office 365/2016/2019/2021/2024: Latest security update via Microsoft Update

  1. Check your current Microsoft Office version by opening any Office app, going to File > Account > About [App]
  2. For Office 365 Apps and Office 365 Copilot: Ensure automatic updates are enabled and run Microsoft Update to receive the latest patches
  3. For Office 2016, 2019, and Office Long Term Servicing Channel (2021, 2024): Apply the latest security updates from Microsoft Update or download from the Microsoft Update Catalog
  4. For Office Online Server: Upgrade to version 16.0.10417.20027 or later from the Microsoft Update Catalog or Volume Licensing Service Center
  5. After updating, restart all Office applications and verify the version number matches the fixed release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 365 Apps Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49697 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-49697 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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