dbcve.org
365 AppsApplication · Microsoft

CVE-2025-62558

HIGH · 7.8 CVSS v3.1 Published 2025-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Word 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

A use-after-free vulnerability exists in Microsoft Office Word where memory is accessed after it has been freed, allowing an attacker to manipulate memory and execute arbitrary code locally on the affected system.

MitigationApply Microsoft security updates for Office Word as soon as patches are released; prioritize patching given the high severity and code execution capability.

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
OfficeApplication
Affected:= 2019
Office Long Term Servicing ChannelApplication
Affected:= 2021= 2024
Sharepoint ServerApplication
Affected:= 2016= 2019
WordApplication
Affected:= 2016

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 Word version
    Open Microsoft Word, go to File > Account > About Word, or check the version in File > Help > About Microsoft Word. Alternatively, check the registry at HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\ClickToRun\RegistryPath or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Common\InstallRoot for the version value.
    Affected if The displayed version matches 2016, 2019, 2021, or 2024, or the product is listed as Microsoft 365 Apps.
  2. Confirm Office product type
    Check if the installation is Microsoft 365 Apps (subscription), standalone Microsoft Office 2019/2016, or Microsoft Office Long Term Servicing Channel (LTSC) 2021/2024. This can be found in Word under File > Account > About Word, or in Windows Programs and Features.
    Affected if The product is any version of Microsoft 365 Apps, Office 2019, Office LTSC 2021, Office LTSC 2024, or standalone Word 2016.
  3. Check SharePoint Server version if applicable
    If SharePoint Server is running, verify its version via SharePoint Administration Center (/_admin/SystemStatus.aspx) or by checking the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\SharePointServer for the DisplayVersion value.
    Affected if SharePoint Server 2016 or 2019 is installed, as these versions include vulnerable Word parsing components.
  4. Verify Word is actively used
    Confirm that Microsoft Word is installed and has been launched on the system, even if not actively in use, as the vulnerability triggers when Word processes a specially crafted file.
    Affected if Word executable (WINWORD.EXE) exists on the system and the version matches the affected versions listed.

If Microsoft Word version 2016, 2019, 2021, or 2024 is installed, or Microsoft 365 Apps with Word is in use, or SharePoint Server 2016/2019 is running, the environment is potentially affected by this use-after-free vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates for Office Word as soon as patches are released; prioritize patching given the high severity and code execution capability.

Recommended fix Moderate confidence

Latest Microsoft Office/Word security updates via Microsoft Update or Microsoft 365 subscription updates

  1. Check for Microsoft Updates via Windows Update or the Microsoft Update Catalog
  2. Locate and install the latest security updates for Microsoft Office and Microsoft 365 Apps
  3. For SharePoint Server, apply the corresponding security update from Microsoft Update Catalog
  4. Restart affected applications after applying updates
  5. Verify the update was successful by checking installed updates
Caveat Standard update - minimal risk; ensure backups of critical documents before updates as a precaution

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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