dbcve.org
365 AppsApplication · Microsoft

CVE-2025-62564

HIGH · 7.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 16.0.10417.20075 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Out-of-bounds read 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 confidence

This is an out-of-bounds read vulnerability in Microsoft Office Excel that allows an unauthorized attacker to execute code locally. The vulnerability occurs when Excel processes specially crafted files, causing the application to read memory beyond allocated buffer boundaries, potentially exposing sensitive data and enabling arbitrary code execution.

MitigationApply Microsoft security updates for Excel as soon as they become available. Avoid opening Excel files from untrusted or unknown sources, and ensure endpoint protection software is active and up-to-date.

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
ExcelApplication
Affected:= 2016
OfficeApplication
Affected:= 2019
Office Long Term Servicing ChannelApplication
Affected:= 2021= 2024
Office Online ServerApplication
Affected:< 16.0.10417.20075

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

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

  1. Verify Excel is installed
    Check for Excel executable: Look for excel.exe in typical installation paths such as C:\Program Files\Microsoft Office\root\Office##\EXCEL.EXE or C:\Program Files (x86)\Microsoft Office\root\Office##\EXCEL.EXE, or search using Get-Process Excel in PowerShell
    Affected if Excel.exe is found running or installed on the system
  2. Determine Excel desktop application version
    Open Excel, go to File > Account > About Excel, or run excel /version from Command Prompt, or check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\Excel\ProductReleaseIDs
    Affected if Version is 2016, 2019, 2021, or 2024, or if using Microsoft 365 Apps (any version)
  3. Determine Office version for Office Long Term Servicing Channel
    Open any Office app, go to File > Account > About [App], or check registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\LTSC\Configuration for version details
    Affected if Office LTSC version is 2021 or 2024
  4. Check Office Online Server version
    On the server running Office Online Server, open SharePoint Management Shell and run Get-OfficeOnlineServerVersion, or check the version number in Programs and Features for Microsoft Office Online Server
    Affected if Office Online Server version is lower than 16.0.10417.20075

The environment is affected if any Excel desktop version (2016, 2019, 2021, 2024) or Microsoft 365 Apps is installed, or if Office Online Server version is below 16.0.10417.20075, and the system opens untrusted Excel files.

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.20075 or later
Fixed in 16.0.10417.20075
Interim mitigation

Apply Microsoft security updates for Excel as soon as they become available. Avoid opening Excel files from untrusted or unknown sources, and ensure endpoint protection software is active and up-to-date.

Recommended fix High confidence

Microsoft 365 Apps: latest version via automatic updates; Office LTSC 2024: apply December 2024 or later security updates; Office LTSC 2021: apply December 2024 or later security updates; Office 2019: apply December 2024 or later security updates; Office 2016: apply December 2024 or later security u

  1. Check for updates via Windows Update or Microsoft Update for your Office installation
  2. For Microsoft 365 (Office 365) Apps: Ensure automatic updates are enabled or manually check for updates in any Office app (File > Account > Update Options > Update Now)
  3. For Office 2016, Office 2019, Office LTSC 2021, and Office LTSC 2024: Apply the latest security updates from Microsoft Update Catalog or Windows Update
  4. For Office Online Server: Update to version 16.0.10417.20075 or later
  5. Verify the update was applied successfully by checking the installed version in any Office app (File > Account > About Excel)
Caveat Standard Office update with no expected breaking changes for end users

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

Fix this in 365 Apps Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62564 — 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-62564 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