dbcve.org
365 AppsApplication · Microsoft

CVE-2025-62200

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

Untrusted pointer dereference in Microsoft Office Excel allows an unauthorized attacker to execute code locally. This is a memory corruption vulnerability where the software dereferences a pointer without validating its integrity, potentially leading to arbitrary code execution with the current user's privileges.

MitigationApply Microsoft security updates for Excel immediately. Until patches are available, restrict Excel file handling to trusted sources and monitor for suspicious Office process behavior.

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
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. Identify installed Excel version
    Locate the Excel executable (typically in C:\Program Files\Microsoft Office\root\Office16\ or similar path) and check its file properties, or open Excel and go to File > Account > About Excel. Alternatively, run 'Get-ItemProperty -Path "C:\Program Files\Microsoft Office\root\Office16\EXCEL.EXE" | Select-Object VersionInfo' in PowerShell
    Affected if The installed version matches any of these: Microsoft 365 Apps (any version), Excel 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, or Office Online Server versions before 16.0.10417.20068
  2. Determine if Microsoft 365 Apps with Excel is present
    Check for Microsoft 365 subscriptions by opening any Office app, going to File > Account, or checking Add/Remove Programs for 'Microsoft 365' entries
    Affected if Microsoft 365 Apps is installed (all versions are affected per the advisory)
  3. Check Office Online Server version
    If hosting Office Online Server, run 'Get-OfficeWebAppsFarm' in PowerShell on the server, or check the installed version of ExcelOnline.aspx or the Office Web Apps service
    Affected if Office Online Server version is less than 16.0.10417.20068 (any version below this threshold)
  4. Verify Excel is in use or processable
    Confirm Excel is actively installed and accessible on the system; this vulnerability is triggered when processing specially crafted Excel files
    Affected if Excel software is installed and can be executed (the vulnerability exists in the code regardless of whether a malicious file has been opened)

A system is affected if it runs any version of Excel from Microsoft 365 Apps, Excel 2016, Office 2019, Office LTSC 2021, Office LTSC 2024, or Office Online Server versions before 16.0.10417.20068.

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 immediately. Until patches are available, restrict Excel file handling to trusted sources and monitor for suspicious Office process behavior.

Recommended fix Moderate confidence

Apply Microsoft Security Update for CVE-2025-62200 (specific KB number available via MSRC)

  1. Open Microsoft Excel and go to File > Account > Update Options
  2. Select 'Update Now' to download and install the latest Microsoft security updates
  3. Alternatively, navigate to Microsoft Update Catalog (catalog.update.microsoft.com) and search for CVE-2025-62200
  4. Download and install the appropriate security update for your Office version
  5. Restart Excel and verify the update was installed by checking File > Account > Update Options > View update history
  6. For Office Online Server, apply update 16.0.10417.20068 or later from Microsoft Update
Caveat Standard Office security update - 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
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
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,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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