dbcve.org
365 AppsApplication · Microsoft

CVE-2025-62202

HIGH · 7.1 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 16.0.10417.20068 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

This is an out-of-bounds read vulnerability in Microsoft Office Excel where the software reads memory beyond allocated buffer boundaries. An attacker could exploit this by crafting a malicious Excel file that, when opened locally, allows unauthorized disclosure of sensitive information from the application's memory space. The 'local' attack vector indicates the attacker needs some form of local access or must trick a user into opening a specially crafted file.

MitigationApply Microsoft security updates for Excel as they become available through standard patch management processes, and exercise caution with Excel files from untrusted sources.

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

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 installation
    Check for Excel.exe on the system - typical paths include C:\Program Files\Microsoft Office\root\Office16\Excel.exe or C:\Program Files (x86)\Microsoft Office\root\Office16\Excel.exe. On Windows, also check Add/Remove Programs or run 'appwiz.cpl' to list installed Microsoft Office products.
    Affected if Excel is not installed on the system.
  2. Determine installed Excel version
    Open Excel, go to File > Account > About Excel. Alternatively, run 'winver' for Windows version, or use 'cliconfg' or check registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration for Microsoft 365/Office versions.
    Affected if Unable to determine the version.
  3. Compare version against affected Microsoft Excel desktop releases
    Match the installed version number: Excel 2016, Excel 2019, Excel 2021, Excel 2024, or any version of Microsoft 365 Apps are all affected. For desktop Office products, note that versions 2016, 2019, 2021, and 2024 are listed as affected.
    Affected if The installed version is Excel 2016, 2019, 2021, 2024, or any Microsoft 365 Apps version.
  4. Check Microsoft Office Online Server version if applicable
    If hosting Office Online Server, check the version at Administration Center or run Get-OfficeWebAppsServer PowerShell command, or inspect the installed build number in Programs and Features.
    Affected if Office Online Server version is lower than 16.0.10417.20068.
  5. Assess exposure to untrusted Excel files
    Determine whether users in the environment routinely open Excel files from external sources, attachments, or downloads - this is the attack vector required for exploitation.
    Affected if Users open Excel files from untrusted or unknown sources.

A system is affected if it runs any version of Microsoft Excel 2016, 2019, 2021, 2024, Microsoft 365 Apps, or Office Online Server versions below 16.0.10417.20068, and users could open maliciously crafted 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.20068 or later
Fixed in 16.0.10417.20068
Interim mitigation

Apply Microsoft security updates for Excel as they become available through standard patch management processes, and exercise caution with Excel files from untrusted sources.

Recommended fix Moderate confidence

Office Online Server: 16.0.10417.20068 or later; Microsoft 365 Apps: Latest version via Microsoft Update

  1. Ensure Microsoft Office automatic updates are enabled and allow updates to install
  2. For Microsoft 365 Apps: Run Microsoft Update to receive the latest security patches for this vulnerability
  3. For Office Online Server: Upgrade to version 16.0.10417.20068 or later
  4. Verify the update was applied by checking Office application version information
  5. For Excel 2016, Office 2019, Office LTSC 2021, and Office LTSC 2024: Apply the corresponding security update from Microsoft Update or the Microsoft Update Catalog
Caveat Standard Office update risks - updates are generally backward compatible but test in non-production environment first if concerned

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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