dbcve.org
365 AppsApplication · Microsoft

CVE-2025-62562

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 Outlook 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 Outlook allows an attacker to achieve local code execution through a specially crafted email or attachment. The vulnerability stems from improper memory management where the application attempts to access memory after it has been freed, potentially enabling arbitrary code execution in the context of the current user.

MitigationApply Microsoft security updates for Microsoft Office Outlook as soon as they become available through standard patch management processes, and consider restricting email attachment handling for untrusted sources 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
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. Confirm Microsoft Outlook installation
    Open Outlook and go to File > Office Account or File > Account Settings > About Outlook. Alternatively, check Programs and Features for Microsoft Outlook.
    Affected if Microsoft Outlook is installed on the system
  2. Identify Outlook version
    Run 'outlook.exe /version' from Command Prompt or check Help > About Microsoft Outlook within the application.
    Affected if Version matches Microsoft 365 Apps (any), Office 2019, Office LTSC 2021, Office LTSC 2024, SharePoint Server 2016, SharePoint Server 2019, or Word 2016 as listed in affected products
  3. Verify Outlook process is in use
    Open Task Manager and look for 'OUTLOOK.EXE' running under background or foreground processes.
    Affected if Outlook is actively running and processing email or attachments
  4. Check email attachment handling
    In Outlook, go to File > Options > Trust Center > Trust Center Settings > Attachment Handling. Note: There is no specific registry or config that disables this vulnerability; this check confirms the attack surface is present.
    Affected if User handles external emails with attachments (normal Outlook operation confirms exposure)
  5. Determine user context
    Check which account Outlook runs under via Task Manager > Details > OUTLOOK.EXE > User Name column.
    Affected if Outlook runs under a user account with elevated privileges (the vulnerability executes in that user context)

A user is affected if Microsoft Outlook is installed and running any of the listed versions, as the use-after-free flaw can be triggered when processing specially crafted emails or attachments.

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 Outlook as soon as they become available through standard patch management processes, and consider restricting email attachment handling for untrusted sources until patches are deployed.

Recommended fix Moderate confidence

Latest Microsoft Office version available via Microsoft Update (patch released via MSRC)

  1. Check for Microsoft Office updates via File > Account > Update Options > Update Now in any Office application
  2. Alternatively, navigate to Microsoft Update Catalog (catalog.update.microsoft.com) and search for CVE-2025-62562 to download the specific patch
  3. Ensure Microsoft Office is updated to the latest patched version available from Microsoft Update
  4. For SharePoint Server, apply the latest Cumulative Update from the Microsoft SharePoint Server update catalog
Caveat Standard Office update—review Microsoft release notes for any feature changes in your specific version

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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