dbcve.org
365 AppsApplication · Microsoft

CVE-2026-32190

HIGH · 8.4 CVSS v3.1 Published 2026-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
No privileges Zero-click

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 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) vulnerability in Microsoft Office enables an unauthenticated attacker to execute arbitrary code locally on the affected system. The vulnerability stems from improper memory management, allowing an attacker to manipulate freed memory objects to achieve code execution.

MitigationApply vendor-supplied Microsoft Office security patches when available; prioritize patch deployment given the high CVSS score and local code execution capability. Consider restricting document-based file handling and macros as a defense-in-depth measure.

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
OfficeApplication
Affected:= 2016= 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/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. Check if Microsoft Office is installed
    Open Control Panel > Programs and Features, or run: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Microsoft Office*'} | Select-Object DisplayName, DisplayVersion
    Affected if No Microsoft Office product appears in the installed programs list, meaning the system is not affected.
  2. Identify the exact Office version number
    For Office click-to-run: Open Command Prompt and run: cd /d "%ProgramFiles%\Microsoft Office\root\Office16" (adjust 16 to 15 for Office 2013, 17 for Office 2019, etc.), then run: odiag.exe /report or check File > Account in any Office app. For MSI installations: Check registry key HKLM\Software\Microsoft\Office\ClickToRun\Configuration or HKLM\Software\Microsoft\Office\{version}\Common\InstallRoot
    Affected if The detected version cannot be determined or does not match any Microsoft Office product.
  3. Compare installed version against affected ranges
    Verify the version matches: Microsoft 365 Apps (any version), Office 2016, Office 2019, Office 2021 LTSC, or Office 2024 LTSC. Note the exact version number from step 2.
    Affected if The installed version is NOT one of: Microsoft 365 Apps (any version), Office 2016, Office 2019, Office 2021 LTSC, or Office 2024 LTSC.
  4. Confirm the specific Office application component
    This UAF vulnerability affects the core Office framework. No specific feature toggle is required. The vulnerability exists in how Office handles memory during document processing.
    Affected if Microsoft Office is installed but is not running any application component (Word, Excel, PowerPoint, Outlook, etc.).

A system is affected if Microsoft Office is installed and the version matches Microsoft 365 Apps (any version), Office 2016, Office 2019, Office 2021 LTSC, or Office 2024 LTSC.

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 vendor-supplied Microsoft Office security patches when available; prioritize patch deployment given the high CVSS score and local code execution capability. Consider restricting document-based file handling and macros as a defense-in-depth measure.

Recommended fix Moderate confidence
  1. Open any Microsoft Office application (e.g., Word) and go to File > Account > Update Options > Update Now to trigger a check for the latest updates.
  2. Alternatively, open Windows Update (or the Microsoft Update Catalog) and check for the newest security updates for Microsoft Office.
  3. Locate and install the security update that addresses CVE‑2026‑32190 (refer to the Microsoft Security Response Center for the specific patch).
  4. After installation, restart Office and verify the update is listed in the update history.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 365 Apps Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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