dbcve.org
365 AppsApplication · Microsoft

CVE-2025-54902

HIGH · 7.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 16.0.10417.20047 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

An out-of-bounds read vulnerability in Microsoft Office Excel allows a local attacker to execute arbitrary code. The vulnerability stems from improper bounds checking when processing Excel files, potentially enabling memory corruption that could be weaponized for code execution in the user's context.

MitigationApply Microsoft security updates when released; until then, avoid opening untrusted Excel files, enable Protected View in Excel, and implement email gateway filtering for suspicious attachments.

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.20047

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. Determine installed Excel version
    Open Excel, go to File > Account > About Excel (or right-click excel.exe in Program Files/Microsoft Office and select Properties > Details tab)
    Affected if Version shows 2016, 2019, 2021, or 2024, or if using Microsoft 365 Apps (any version)
  2. Check Office 365 subscription version
    In Excel, go to File > Account > View Updates, or open any Office app, go to File > Account and look for 'Update Options' to see if it's a subscription version
    Affected if Using Microsoft 365 Apps subscription (all versions are affected per the CVE)
  3. Identify Office Long Term Servicing Channel version
    Open Excel, go to File > Account > About Excel; LTSC versions typically display as version numbers like 16.0.14332.x or similar with no subscription indicator
    Affected if Version displays as Office LTSC 2021 or Office LTSC 2024 specifically
  4. For Office Online Server environments, check server version
    Open SharePoint Management Shell and run: Get-OfficeWebAppsServer | Select-Object Build; or check the installed version of OfficeWebApps.msi
    Affected if Build version is lower than 16.0.10417.20047

You are affected if you have Microsoft Excel 2016, 2019, 2021, 2024, Microsoft 365 Apps (any version), or Office Online Server with build below 16.0.10417.20047.

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.20047 or later
Fixed in 16.0.10417.20047
Interim mitigation

Apply Microsoft security updates when released; until then, avoid opening untrusted Excel files, enable Protected View in Excel, and implement email gateway filtering for suspicious attachments.

Recommended fix Moderate confidence

Microsoft security updates (patch to latest available for your Office/365 version); Office Online Server: 16.0.10417.20047 or later

  1. Open Microsoft Excel and go to File > Account > Update Options > Update Now to check for and apply the latest Microsoft updates
  2. Alternatively, open Windows Update (Settings > Update & Security > Windows Update) and check for updates to install the latest Office security patches
  3. For Office Online Server, upgrade to version 16.0.10417.20047 or later by installing the latest Office Online Server update from the Microsoft Update Catalog
  4. After updating, verify the update was applied by checking Excel's version information under File > Account
Caveat Standard Office updates typically have minimal breaking changes; test critical Excel macros and add-ins after applying updates in enterprise environments

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

Fix this in 365 Apps Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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