dbcve.org
365 AppsApplication · Microsoft

CVE-2025-62557

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 →
80/100
Remediation priority · High
Zero-click

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 allows an unauthorized attacker to execute code locally by exploiting freed memory references, potentially achieving arbitrary code execution through heap manipulation.

MitigationApply Microsoft security updates for Microsoft Office to patch the use-after-free vulnerability or upgrade to a patched version of Office.

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:all versions
OfficeApplication
Affected:= 2016= 2019
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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 the installed Microsoft Office product
    Open any Office application (Word, Excel, etc.), go to File > Account, and note the product name and version shown. Alternatively, check the properties of WINWORD.EXE in the Office installation folder.
    Affected if If the product is Microsoft 365 Apps, Microsoft 365 Copilot, Office 2016, Office 2019, Office LTSC 2021, or Office LTSC 2024
  2. Determine if Microsoft 365 Apps or Copilot has the latest updates
    In any Microsoft 365 app, go to File > Account > Update Options and verify the update status. Check if updates are enabled and the last update date.
    Affected if If the product is Microsoft 365 Apps or Microsoft 365 Copilot and updates are disabled, not applied, or the installation predates the security patch release date
  3. Check the exact build version for Office 2016, 2019, LTSC 2021, or LTSC 2024
    In the Office application, go to File > Account > About [AppName] to display the exact build number (e.g., 16.0.xxxxx.xxxx).
    Affected if If the installed version is Office 2016, Office 2019, Office LTSC 2021, or Office LTSC 2024 regardless of build, as these are explicitly listed as affected
  4. Verify the Office installation channel
    Check the registry key HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration or examine the product name displayed in Account settings to confirm if it is a subscription (Microsoft 365) or perpetual license (LTSC/Retail).
    Affected if If the installation is any channel of the affected products listed

The environment is affected if Microsoft Office is installed and the version matches Microsoft 365 Apps, Microsoft 365 Copilot, Office 2016, Office 2019, Office LTSC 2021, or Office LTSC 2024, and the applicable security patch has not been applied.

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 Microsoft Office to patch the use-after-free vulnerability or upgrade to a patched version of Office.

Recommended fix Moderate confidence

Latest Microsoft Office updates via Microsoft Update or MSRC security bulletin for CVE-2025-62557

  1. Check Microsoft Update or open any Office application and go to File > Account > Update Options > Update Now to receive the latest security patches
  2. Alternatively, navigate to https://www.catalog.update.microsoft.com/ and search for CVE-2025-62557 to download the appropriate security update for your specific Office version
  3. Ensure Microsoft Office is updated to the latest available version as specified in the corresponding MSRC security update release
Caveat Standard Office update; minimal risk but test critical documents after major version jumps

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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