dbcve.org
365 AppsApplication · Microsoft

CVE-2025-59232

HIGH · 7.1 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 16.0.10417.20059 or later.
See remediation →
74/100
Remediation priority · Elevated
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 disclose information 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

An out-of-bounds read vulnerability exists in Microsoft Office Excel that allows a local unauthorized attacker to read sensitive information from memory beyond intended boundaries. This information disclosure flaw does not require user interaction or elevated privileges.

MitigationApply the latest Microsoft security updates for Microsoft Office Excel as released through the official Microsoft Security Response Center. Prior to deployment in production, validate compatibility within the organization's Office environment.

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

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
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 Microsoft Excel is installed
    Open Excel, go to File > Account > About Excel, or run 'winver' and check installed programs in Control Panel > Programs and Features
    Affected if Microsoft Excel is present on the system
  2. Determine installed Excel version number
    In Excel: File > Account > About Excel displays the version (e.g., 16.0.xxxxx.xxxxx). Alternatively, run 'excel /?' from Command Prompt or check HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration in Registry
    Affected if Version matches or falls within the affected ranges (2016, 2019, 2021, 2024, or any Microsoft 365 version)
  3. Confirm product type and channel
    Check File > Account > About Excel for 'Microsoft 365' or check Registry under HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration for 'UpdateToVersion' or OfficeMgmtCOM for channel info
    Affected if Product is Microsoft 365 Apps (all versions affected), Office 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, Office Online Server < 16.0.10417.20059, or SharePoint Server 2016/2019
  4. Verify Excel file handling is enabled
    The vulnerability triggers when Excel opens specially crafted files. Check if Excel is configured to open files from network locations or untrusted sources (File > Options > Trust Center > Trust Center Settings > Protected View)
    Affected if Excel can open or processes files from any source, as no user interaction is required for exploitation

A system is affected if it runs any version of Microsoft Excel from 2016, 2019, 2021, 2024, Microsoft 365 Apps, or Office Online Server prior to build 16.0.10417.20059, regardless of user privileges.

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.20059 or later
Fixed in 16.0.10417.20059
Interim mitigation

Apply the latest Microsoft security updates for Microsoft Office Excel as released through the official Microsoft Security Response Center. Prior to deployment in production, validate compatibility within the organization's Office environment.

Recommended fix High confidence

Apply Microsoft security updates for CVE-2025-59232 (check Microsoft Update Catalog for the specific KB number)

  1. Open Microsoft Word (or any Office app), go to File > Account > Update Options > Update Now to apply the latest Microsoft 365 updates
  2. Alternatively, open Windows Update (Settings > Update & Security > Windows Update) and check for updates to install all pending Microsoft security patches
  3. For Office 2016, 2019, LTSC 2021, and 2024: Run Microsoft Update or open any Office app and go to File > Account > Update Options > Update Now
  4. For Office Online Server: Install the latest cumulative update for Office Online Server that addresses CVE-2025-59232 from the Microsoft Update Catalog
  5. For SharePoint Server 2016/2019: Apply the relevant security update from Microsoft Update Catalog that addresses this vulnerability
Caveat Standard Office security updates typically have no breaking changes; they are cumulative and include prior security fixes

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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