Patch tracker / CVE reference / CVE-2026-50467

CVE-2026-50467

CVE-2026-50467 is a high severity Microsoft vulnerability with a CVSS score of 7.8. Microsoft has shipped the fix: deploy the update below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

7.8

CVSS

<1%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability <1%. CVSS 7.8 (High).

This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2026-50467

CVE-2026-50467 is a High severity (CVSS 7.8) remote code execution flaw in Microsoft Office 2019 (32-bit and 64-bit) and Microsoft 365 Apps for Enterprise on 32-bit systems. The 7.8 score with local attack characteristics points to a document-triggered path, meaning a user opening a crafted Office file is the likely exposure vector. It is not in CISA KEV and has no known ransomware use yet, but Office RCE bugs are common phishing payloads once patches reveal the mechanism.

Do this: Deploy the Office and Microsoft 365 Apps updates covering CVE-2026-50467 to all 2019 and 32-bit Enterprise installs, prioritizing users who routinely open external documents.

AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-50467

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2026-50467 (source: https://senserva.com/cve/CVE-2026-50467.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-50467: High severity Microsoft vulnerability, CVSS 7.8
- EPSS 30-day exploitation probability: <1%
- Actively exploited (CISA KEV): no
- Fixed by: KB5002887
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Schedule normally

No exploitation observed: not in the CISA KEV catalog, EPSS under 1%.

Fixed by KB5002887. Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Official patch(es) for CVE-2026-50467

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing update KB5002887 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security update below to fix CVE-2026-50467. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.

KB5002887

Scope and sources

Affected products

Fixed by the same update

CVE-2026-55045 CVE-2026-50301 CVE-2026-50314 CVE-2026-50665 CVE-2026-55018 CVE-2026-55022 CVE-2026-55056 CVE-2026-55125

Authoritative references

Official CVE record (cve.org)NVD detail Microsoft MSRC FIRST.org EPSS

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.