dbcve.org
365 AppsApplication · Microsoft

CVE-2026-48580

MEDIUM · 5.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 16.0.10417.20175 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges Patch available 5 weeks old

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
Untrusted pointer dereference in Microsoft Office Excel allows an unauthorized attacker to disclose information locally.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced from public web coverage — external links open in a new tab.

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

An untrusted pointer dereference vulnerability in Microsoft Office Excel allows a local attacker to read sensitive information from memory due to improper validation of pointers before dereferencing. This is an information disclosure vulnerability with local attack vector.

MitigationApply the latest Microsoft Office security updates to address the pointer dereference vulnerability. Users should ensure their Microsoft Office installations are current through Windows Update or manual patch deployment.

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
Microsoft 365Application
Affected:all versions
Office 2019Application
Affected:all versions
Office 2021Application
Affected:all versions
Office 2024Application
Affected:all versions
Office Online ServerApplication
Affected:< 16.0.10417.20175

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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 Control Panel > Programs and Features, look for Microsoft Excel in the Microsoft Office installation list. Or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell and search for Excel entries.
    Affected if Excel is not present in the installed programs list, the system is not affected.
  2. Identify the installed Office/Excel version
    Open Excel, go to File > Account > About Excel. Alternatively, run 'winword.exe /?' or 'excel.exe /?' from Command Prompt to see version information, or check HKEY_CLASSES_ROOT\Excel.Application\CurVer in the Windows Registry.
    Affected if The version falls within any of the affected ranges: Microsoft 365 Apps (all), Excel 2016, Microsoft 365 (all), Office 2019 (all), Office 2021 (all), Office 2024 (all), or Office Online Server version below 16.0.10417.20175.
  3. Verify the Excel executable is present
    Check for excel.exe in typical installation paths such as C:\Program Files\Microsoft Office\root\Office16\ (path varies by version number) or C:\Program Files (x86)\Microsoft Office\root\Office16\.
    Affected if The excel.exe file does not exist in standard Office installation directories, indicating Excel is not installed.
  4. Check if Excel is configured to open files automatically
    Inspect Excel macro security settings (File > Options > Trust Center > Trust Center Settings > Macro Settings) and file association handlers. This vulnerability requires a user to open a malicious file.
    Affected if The system has no Excel-related file associations or Excel is completely disabled, exploitation is unlikely.

A system is affected if Microsoft Excel is installed and the installed version matches any of the listed affected products and version ranges, particularly for Office Online Server versions prior to 16.0.10417.20175.

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
Upgrade available Upgrade to 16.0.10417.20175 or later
Fixed in 16.0.10417.20175
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the latest Microsoft Office security updates to address the pointer dereference vulnerability. Users should ensure their Microsoft Office installations are current through Windows Update or manual patch deployment.

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 the upgrade done

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-2026-48580 — 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-2026-48580 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