cve.bz

CVE-2026-21509 Microsoft Office Security Feature Bypass Vulnerability

7.8 highKEVEPSS 71%

High (7.8) in Microsoft Office. In CISA KEV since 2026-01-26. EPSS 71% estimated probability of exploitation activity in the next 30 days.

On this page
Reliance on untrusted inputs in a security decision in Microsoft Office allows an unauthorized attacker to bypass a security feature locally.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
71% (unchanged from 71% a week ago; 71% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-01-26, due 2026-02-16
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2026-01-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-807 Reliance on Untrusted Inputs in a Security Decision
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-21509 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-21509?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-21509?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-21509 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft 365 Apps for Enterprisefrom 16.0.1 before https://aka.ms/OfficeSecurityReleases
Microsoft Office 2016from 16.0.0 before 16.0.5539.1001
Microsoft Office 2019from 19.0.0 before 16.0.10417.20095
Microsoft Office LTSC 2021from 16.0.1 before https://aka.ms/OfficeSecurityReleases
Microsoft Office LTSC 2024from 16.0.0 before https://aka.ms/OfficeSecurityReleases

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • gavz/CVE-2026-21509-PoC 44 stars, created
    Educational PoC for CVE‑2026‑21509 (Microsoft Office security feature bypass). Generates a harmless DOCX with dummy OLE artifacts to study …
  • kimstars/Ashwesker-CVE-2026-21509 11 stars, created
    CVE-2026-21509
  • suuhm/CVE-2026-21509-handler 8 stars, PowerShell, created
    PowerShell script to check, apply, and test the Kill-Bit protection for the CVE-2026-21509 Microsoft Office zero-day vulnerability affectin…
  • decalage2/detect_CVE-2026-21509 3 stars, Python, created
    YARA rule and python script to detect potential exploits for the CVE-2026-21509 vulnerability in MS Office
  • SimoesCTT/CTT-MICROSOFT-OFFICE-OLE-MANIFOLD-BYPASS-CVE-2026-21509 3 stars, Python, created
    CVE-2026-21509 is a critical bypass in the Microsoft Office OLE (Object Linking and Embedding) validation engine. While standard "laminar" …
5 more

References

Check your stackJSON