dbcve.org
365 AppsApplication · Microsoft

CVE-2026-26112

HIGH · 7.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 16.0.10417.20102 or later.
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
Untrusted pointer dereference 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

Untrusted pointer dereference vulnerability in Microsoft Office Excel allows an unauthorized attacker to execute code locally due to improper memory handling in Excel's file parsing operations.

MitigationApply Microsoft security updates for Office Excel as they become available, or upgrade to the latest supported Microsoft Office version to address the vulnerability.

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:< 16.0.10417.20102

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. Identify installed Microsoft Excel version
    Open Excel, go to File > Account > About Excel (or File > Help in newer versions). Alternatively, open Excel and go to File > Account > View Updates in the Office app
    Affected if Version shows Excel 2016, Excel 2019, or Excel from Microsoft 365 Apps (any version)
  2. Identify installed Microsoft Office version
    Open any Office app (like Word), go to File > Account > About [App]. The version is displayed in the first line of the dialog. On Windows, you can also check via Control Panel > Programs and Features > Microsoft Office
    Affected if Office version shows 2016, 2019, 2021 LTSC, or 2024
  3. Check Office Online Server version
    Open SharePoint Management Shell and run: Get-OfficeOnlineServerMachine. Or access the Office Online Server health dashboard at /hosting/discovery
    Affected if Office Online Server version is lower than 16.0.10417.20102
  4. Confirm Excel component is present
    Verify Microsoft Excel is installed by checking Programs and Features in Control Panel, or by running 'winword /version' in Command Prompt which shows Office installation details including Excel
    Affected if Excel component is listed as installed and version matches affected ranges

A user is affected if they have Microsoft Excel 2016, 2019, Microsoft 365 Apps (any version), Office 2019, Office LTSC 2021, Office LTSC 2024, or Office Online Server version below 16.0.10417.20102 installed.

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
Upgrade available Upgrade to 16.0.10417.20102 or later
Fixed in 16.0.10417.20102
Interim mitigation

Apply Microsoft security updates for Office Excel as they become available, or upgrade to the latest supported Microsoft Office version to address the vulnerability.

Recommended fix Moderate confidence

Microsoft 365 current channel or version 16.0.10417.20102 for Office Online Server

  1. Verify current Microsoft Office version by opening any Office app, going to File > Account > About [App]
  2. For Microsoft 365/Office 365 users: Ensure automatic updates are enabled and install latest updates via File > Account > Update Options > Update Now
  3. For Office 2016, 2019, LTSC 2021, 2024: Apply the latest cumulative security update from Microsoft Update Catalog or Windows Update
  4. For Office Online Server: Update to version 16.0.10417.20102 or later from the Microsoft Update Catalog
  5. After updating, verify the fix by checking File > Account > About [App] shows the patched version
  6. Restart all Office applications and confirm normal functionality
Caveat Standard Office update risks - verify critical workflows in test environment before broad deployment

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

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