dbcve.org
365 AppsApplication · Microsoft

CVE-2025-32705

HIGH · 7.8 CVSS v3.1 Published 2025-05-13
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
Out-of-bounds read 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

An out-of-bounds read vulnerability in Microsoft Office Outlook allows an unauthorized attacker to execute code locally on the affected system. The vulnerability stems from improper memory handling when processing certain input in Outlook.

MitigationApply Microsoft security updates for CVE-2025-32705 to all affected Outlook installations as soon as possible.

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
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. Verify Microsoft Outlook is installed
    Open Windows PowerShell and run: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\OUTLOOK.EXE' -ErrorAction SilentlyContinue | Select-Object -ExpandProperty '(default)'
    Affected if The command returns a path to outlook.exe indicating Outlook is installed on the system
  2. Identify the installed Outlook version via Click-to-Run
    Run in PowerShell: (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' -ErrorAction SilentlyContinue).ProductReleaseIds
    Affected if The output contains any release ID, confirming Microsoft 365 Apps version is present (all affected)
  3. Identify the installed Outlook version via registry for Office Click-to-Run
    Run in PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' | Select-Object VersionToReport,ProductReleaseIds
    Affected if The version matches any Microsoft 365 Apps release (all versions affected) or shows Office Long Term Servicing Channel version 2021 or 2024
  4. Identify the installed Outlook version for traditional Office installation
    Run in PowerShell: (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\16.0\Common\InstallRoot' -ErrorAction SilentlyContinue).Version -or (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\15.0\Common\InstallRoot' -ErrorAction SilentlyContinue).Version
    Affected if The version returned corresponds to Office 2021 (16.0) or Office 2024 (16.0) Long Term Servicing Channel
  5. Confirm vulnerability applicability based on product channel
    Run: (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' -ErrorAction SilentlyContinue).UpdateChannel. Compare against: Microsoft 365 Apps (any channel) or LTSC 2021/2024
    Affected if The system runs Microsoft 365 Apps on any update channel, or Office LTSC version 2021 or 2024

The system is affected if Microsoft Outlook is installed and the installation is either Microsoft 365 Apps (any version/channel) or Office LTSC version 2021 or 2024, as these are the specifically listed affected products.

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 CVE-2025-32705 to all affected Outlook installations as soon as possible.

Recommended fix Moderate confidence

Latest Microsoft 365 Apps version (channel-specific) or Office LTSC 2024 with latest patches

  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-32705 to download the specific security update
  3. Ensure Microsoft Office Outlook is updated to the latest version available through your Office 365 subscription or LTSC channel
  4. Verify the update was applied by checking Outlook version information under File > Office Account
Caveat Minimal risk; standard Microsoft security update with no expected breaking changes for typical Outlook usage

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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