dbcve.org
365 AppsApplication · Microsoft

CVE-2025-24082

HIGH · 7.8 CVSS v3.1 Published 2025-03-11
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

A Use After Free (UAF) memory corruption vulnerability in Microsoft Office Excel enables an unauthorized attacker to achieve local code execution. The vulnerability stems from improper memory management where Excel continues referencing a freed memory pointer, potentially allowing an attacker to control reallocated memory and execute arbitrary code.

MitigationApply the latest Microsoft security updates for Microsoft Office/Excel as soon as they become available through Windows Update or the Microsoft Update Catalog. Prioritize patching 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
Office Online ServerApplication
Affected:all versions

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 Excel is installed
    Open Windows Settings > Apps > Apps & features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed Office components
    Affected if Excel is not listed among installed applications, then the system is not affected by this Excel-specific vulnerability
  2. Check Microsoft 365 Apps for Excel version
    Open Excel, go to File > Account > About Excel, or run 'Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" -ErrorAction SilentlyContinue' to read the version from the registry
    Affected if The version displayed begins with a version number that falls within the Microsoft 365 release timeline (all versions are affected)
  3. Check Microsoft Excel 2016 standalone version
    Run 'Get-ItemProperty HKLM:\Software\Microsoft\Office\16.0\Excel\InstallRoot -ErrorAction SilentlyContinue' or open Excel > File > Account > About Excel to see version number
    Affected if Excel version is 2016 (16.0.xxxx) - this specific version is listed as affected
  4. Check Microsoft Office 2019 version
    Run 'Get-ItemProperty HKLM:\Software\Microsoft\Office\19.0\Excel\InstallRoot -ErrorAction SilentlyContinue' or check Excel > File > Account > About Excel
    Affected if Office version shows as 2019 (19.0.xxxx) - this version is listed as affected
  5. Check Office LTSC 2021 or 2024 version
    Run 'Get-ItemProperty HKLM:\Software\Microsoft\Office\21.0\Excel\InstallRoot -ErrorAction SilentlyContinue' for LTSC 2021, or 'HKLM:\Software\Microsoft\Office\24.0\Excel\InstallRoot' for version 2024
    Affected if Excel version corresponds to Office LTSC 2021 (21.0) or 2024 (24.0) - both versions are listed as affected
  6. Check Microsoft Office Online Server presence
    On Windows Server, run 'Get-WindowsFeature -Name OfficeOnlineServer' or check installed programs for 'Office Online Server'
    Affected if Office Online Server is installed - all versions of this component are listed as affected

A system is affected if Microsoft Excel, Microsoft Office 2019, Office LTSC 2021/2024, Microsoft 365 Apps, or Office Online Server is installed, because all versions of these products fall within the affected ranges specified for this CVE.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the latest Microsoft security updates for Microsoft Office/Excel as soon as they become available through Windows Update or the Microsoft Update Catalog. Prioritize patching given the high CVSS score and code execution capability.

Fix this in 365 Apps Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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