dbcve.org
365 AppsApplication · Microsoft

CVE-2025-62203

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
Use after free 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 · high confidence

Use after free vulnerability in Microsoft Office Excel that allows an unauthorized attacker to execute code locally. The memory corruption occurs when Excel improperly handles freed memory objects, potentially enabling arbitrary code execution on the affected system.

MitigationApply Microsoft security updates for Excel as they become available through standard patch management processes, and ensure Office installations are maintained on supported, current versions.

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. Verify Excel is installed
    Open Excel and go to File > Account > About Excel, or run 'winver' and look for Office/Excel in the installed programs list
    Affected if Excel is not installed on the system
  2. Determine Excel version number
    In Excel, go to File > Account > About Excel and note the version displayed (e.g., 16.0.xxxxx.xxxxx)
    Affected if Version cannot be determined or Excel is not accessible
  3. Check Microsoft 365 Apps version
    Open any Office app, go to File > Account > View Updates, or check registry at HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration for VersionToReport
    Affected if Running Microsoft 365 Apps and version is not at latest patched build
  4. Check standalone Excel 2016+ or Office 2019+ version
    Run 'excel /?' from command prompt or check registry at HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration or HKLM\SOFTWARE\Microsoft\Office\16.0\Excel\InstallRoot for version
    Affected if Excel version 2016 or later is installed and not patched to current security release
  5. Check Office Long Term Servicing Channel version
    Check registry at HKLM\SOFTWARE\Microsoft\Office\LTSC\Configuration or use Office Configuration Analyzer Tool to identify LTSC installation
    Affected if LTSC version 2021 or 2024 is installed and not patched
  6. Check Office Online Server version
    On the server, run 'Get-OfficeWebAppsServer' PowerShell cmdlet or check registry at HKLM\SOFTWARE\Microsoft\Office\WebApps\Server\Version for build number
    Affected if Office Online Server version is below 16.0.10417.20068

The system is affected if Microsoft Excel is installed with any version from 2016 onward, or Microsoft 365 Apps, Office 2019+, LTSC 2021/2024, or Office Online Server prior to build 16.0.10417.20068, and the environment has not received the corresponding security update.

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 ensure Office installations are maintained on supported, current versions.

Recommended fix Moderate confidence

Office Online Server: 16.0.10417.20068 or later; Other products: latest Microsoft security patches

  1. Check for Microsoft updates via Windows Update or your organization's patch management system
  2. For Office Online Server, upgrade to version 16.0.10417.20068 or later
  3. Apply the latest Microsoft security updates for Microsoft Office products
  4. Restart affected applications after applying updates
Caveat Standard Office update apply risks - test in non-production environment first if possible

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-62203 — 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-62203 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