dbcve.org
365 AppsApplication · Microsoft

CVE-2026-33114

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
Untrusted pointer dereference in Microsoft Office Word 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 an untrusted pointer dereference vulnerability in Microsoft Office Word. The vulnerability allows an unauthorized attacker to execute code locally by leveraging the pointer dereference flaw, typically through a maliciously crafted Word document opened by the victim.

MitigationApply Microsoft security updates for Office Word when available; until then, use Protected View for untrusted documents, disable macros, and educate users about not opening documents from untrusted sources.

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
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. Verify Microsoft Word installation
    Open Word and go to File > Account, or check for WINWORD.EXE in Program Files (typically C:\Program Files\Microsoft Office\root\Office## or C:\Program Files (x86)\Microsoft Office\root\Office##)
    Affected if Microsoft Word is not installed, the system is not affected by this vulnerability
  2. Identify Office subscription type
    In Word, go to File > Account to view the subscription model. Check if it shows 'Microsoft 365' or 'Office 365' (now Microsoft 365 Apps). Alternatively, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration or HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0 (or 15.0/14.0)\Common\InstallRoot
    Affected if The installation is Microsoft 365 Apps (any version), indicating the system is affected by CVE-2026-33114 because all Microsoft 365 Apps versions are listed as affected
  3. Check LTSC version if not Microsoft 365
    If not Microsoft 365 Apps, open Word and go to File > Account, or run 'winword /?' from Command Prompt to display version information. Look for version numbers 2021 or 2024
    Affected if The installed version is Microsoft Office LTSC 2021 or LTSC 2024, as these specific versions are listed as affected in the CVE details

A system is affected if it runs Microsoft 365 Apps (any version) or Microsoft Office LTSC versions 2021 or 2024, as all these versions are within the affected product ranges specified in CVE-2026-33114.

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 Office Word when available; until then, use Protected View for untrusted documents, disable macros, and educate users about not opening documents from untrusted sources.

Recommended fix Moderate confidence

Apply Microsoft Security Update for Office (specific tuple/value available from MSRC advisory at https://msrc.microsoft.com/update-guide)

  1. Open Microsoft Word and go to File > Account > Update Options > Update Now
  2. Alternatively, open Windows Settings > Update & Security > Windows Update and check for updates
  3. Ensure Microsoft 365 Apps or Office LTSC is updated to the latest security patch release
  4. For enterprise deployments, verify via Microsoft Endpoint Manager or WSUS that the latest Microsoft Office security update (typically released on Patch Tuesday) is deployed
  5. After updating, verify the Office version through File > Account > About Word to confirm the build number reflects the latest security patch
Caveat Standard Office security update with no expected breaking changes; updates are cumulative and include only security fixes

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 / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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