PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-33095 Microsoft CVE debrief

Microsoft Word Remote Code Execution Vulnerability allows an unauthorized attacker to execute code locally due to a use-after-free vulnerability. This vulnerability affects Microsoft Office Word, potentially allowing attackers to exploit it for local code execution. Defenders should prioritize patching and monitoring to prevent potential exploitation. The vulnerability has a high severity with a CVSS score of 7.8. The CVE record and NVD entry provide details on the vulnerability, but limited information is available on exploitation or impact.

Vendor
Microsoft
Product
Microsoft 365 Apps for Enterprise
CVSS
HIGH 7.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-14
Original CVE updated
2026-10-15
Advisory published
2026-04-14
Advisory updated
2026-10-15

Who should care

Defenders responsible for Microsoft Office and Microsoft 365 Apps for Enterprise deployments should assess exposure and apply patches. They should also inventory and monitor installations for potential exposure and implement compensating controls to detect and prevent suspicious activity related to Microsoft Word. Additionally, security teams and vulnerability management teams should prioritize patching and review 3

Why it matters

CVE-2026-33095 is a high-severity vulnerability in Microsoft Word that allows an unauthorized attacker to execute code locally. Defenders should prioritize patching and monitoring to prevent potential exploitation.

  • Verify and apply patches to prevent local code execution
  • Inventory and monitor Microsoft Office and Microsoft 365 Apps for Enterprise installations for potential exposure
  • Implement compensating controls to detect and prevent suspicious activity related to Microsoft Word

Technical summary

A use-after-free vulnerability in Microsoft Office Word allows an unauthorized attacker to execute code locally. The vulnerability is identified as CVE-2026-33095 and has a CVSS score of 7.8, indicating high severity. The vulnerability affects Microsoft Office Word and potentially allows attackers to exploit it for local code execution. There is no information on the root cause or specific exploit details.

Defensive priority

High

Recommended defensive actions

  • Review and apply Microsoft's patch for CVE-2026-33095
  • Inventory Microsoft Office and Microsoft 365 Apps for Enterprise installations to identify potential exposure
  • Monitor for suspicious activity related to Microsoft Word

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but limited information is available on exploitation or impact. The vulnerability is identified as a use-after-free issue in Microsoft Office Word, which could allow an unauthorized attacker to execute code locally. There is no information on known or reported exploitation. Defenders should verify affected product deployments and apply patches accordingly.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-33095 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-33095

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-33095 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-33095

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Microsoft Word Remote Code Execution Vulnerability

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/33xxx/CVE-2026-33095.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33095

    Supplemental source - vendor-advisory, patch

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.