dbcve.org
365 AppsApplication · Microsoft

CVE-2025-27750

HIGH · 7.8 CVSS v3.1 Published 2025-04-08
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 Excel 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

This is a use-after-free memory corruption vulnerability in Microsoft Office Excel. The vulnerability allows a local attacker to execute arbitrary code by exploiting improper memory management where memory is accessed after being freed, potentially leading to code execution with the current user's privileges.

MitigationApply Microsoft security updates for CVE-2025-27750 as they become available through Windows Update or Microsoft Update catalog. Prioritize deployment given the high CVSS score 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
ExcelApplication
Affected:= 2016
OfficeApplication
Affected:= 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
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 Excel is installed
    Open Excel and go to File > Account, or check Programs and Features for Microsoft Excel, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like "*Excel*"}' in PowerShell
    Affected if Excel is not installed on the system
  2. Identify installed Excel version
    In Excel, go to File > Account > About Excel, or run 'winword.exe /?' from Command Prompt, or check registry key HKLM\Software\Microsoft\Office\ClickToRun\Configuration or HKLM\Software\Microsoft\Office\[version]\Excel\InstallRoot
    Affected if Cannot determine the Excel version from the system
  3. Compare version against affected Microsoft 365 Apps range
    For Microsoft 365 subscriptions, run 'Get-ItemProperty "HKLM:\Software\Microsoft\Office\ClickToRun\Configuration" | Select-Object VersionToReport' to get the Click-to-Run version; if unpatched, all versions are affected
    Affected if Running Microsoft 365 Excel and the version is prior to the patched release for CVE-2025-27750
  4. Compare version against affected standalone Excel 2016+
    If using standalone Excel 2016, 2019, 2021, or 2024, compare the file version of C:\Program Files\Microsoft Office\root\OfficeXX\EXCEL.EXE (where XX is version folder) or the registry Version value against known affected version ranges
    Affected if Excel version is 2016 or later and the installation lacks the CVE-2025-27750 security update
  5. Check if Office Click-to-Run is present
    Check for the presence of the Click-to-Run virtualization layer via registry key HKLM\Software\Microsoft\Office\ClickToRun or by observing the Office application startup behavior
    Affected if Office is managed via Click-to-Run and pending updates exist for CVE-2025-27750

The environment is affected if Microsoft Excel (standalone or Microsoft 365) version 2016 or later is installed and the CVE-2025-27750 security update 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 CVE-2025-27750 as they become available through Windows Update or Microsoft Update catalog. Prioritize deployment given the high CVSS score and code execution capability.

Recommended fix Moderate confidence
  1. Open Microsoft Excel or any Office application
  2. Go to File > Account > Update Options > Update Now
  3. Alternatively, open Windows Update (Settings > Update & Security > Windows Update) and check for updates
  4. Install all available Microsoft Office security updates
  5. Restart the computer after installing updates
  6. Verify the update was installed by checking Office version information under File > Account

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-27750 — 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-27750 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