dbcve.org
365 AppsApplication · Microsoft

CVE-2025-62199

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

Use-after-free vulnerability in Microsoft Office enables an unauthorized local attacker to execute arbitrary code by exploiting improper memory management after a memory location has been freed.

MitigationApply Microsoft security updates for Office as they become available; enforce least-privilege user practices and restrict opening of untrusted or unexpected Office documents until patches are deployed.

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
365 CopilotApplication
Affected:< 16.0.19426.20044
ExcelApplication
Affected:= 2016
Office Long Term Servicing ChannelApplication
Affected:= 2021= 2024

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 Microsoft Office products
    Open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to enumerate installed Office products
    Affected if Any Microsoft Office product is installed (the vulnerability affects multiple Office applications)
  2. Check Microsoft 365 Apps version
    Launch any M365 app (e.g., Word or Excel), go to File > Account, and note the version under 'About [app]'. Alternatively, run 'Get-AppxPackage *Microsoft.Office*' in PowerShell to list installed M365 packages and their versions
    Affected if Microsoft 365 Apps is installed (affected versions include all versions)
  3. Check Microsoft 365 Copilot version
    Open the Copilot pane in any M365 application, click the account/settings icon, and note the Copilot version, or check the Office version as above which includes Copilot component versioning
    Affected if M365 Copilot version is lower than 16.0.19426.20044
  4. Check Microsoft Excel version
    Launch Excel, go to File > Account > About Excel, and record the version number (e.g., 16.0.xxxxx.xxxx)
    Affected if Excel version corresponds to Office 2016 (specific build matching the 2016 release)
  5. Check Office Long Term Servicing Channel version
    Launch any Office app, go to File > Account > About [app], and identify if the build indicates LTSC 2021 or LTSC 2024 by the version number (typically 16.0.xxxx.xxxx format for LTSC releases)
    Affected if Office LTSC 2021 or Office LTSC 2024 is installed

A user is affected if they have Microsoft 365 Apps (any version), M365 Copilot below 16.0.19426.20044, Excel 2016, or Office LTSC 2021/2024 installed on their system.

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.19426.20044 or later
Fixed in 16.0.19426.20044
Interim mitigation

Apply Microsoft security updates for Office as they become available; enforce least-privilege user practices and restrict opening of untrusted or unexpected Office documents until patches are deployed.

Recommended fix Moderate confidence

Microsoft 365 Copilot: 16.0.19426.20044 or later; Microsoft 365 Apps: latest version; Office LTSC 2021/2024: apply all available security updates

  1. Check current Microsoft Office version by opening any Office app, going to File > Account > About [App]
  2. For Microsoft 365 Copilot: Ensure version is 16.0.19426.20044 or higher via File > Account > Update Options > Update Now
  3. For Microsoft 365 Apps: Apply latest Microsoft 365 updates via Windows Update or Office Admin Center
  4. For Office LTSC 2021/2024: Apply latest updates from Microsoft Update Catalog or via configured update channel
  5. Verify successful update by rechecking the version number
Caveat Standard Office update risks - ensure compatibility with existing add-ins and macros before deploying enterprise-wide

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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