Skip to content

CVE-2026-21509

Is CVE-2026-21509 real, exploitable, or a false positive? Here's the community verdict.

signals

public sources

Exploited in wild
Yes
CISA KEV
Public exploit
None known
Metasploit/EDB/PoC
Base severity
7.8 High
CVSS
Exploitation prob.
72%
FIRST EPSS
Weakness
CWE-807
CWE

Confirmed exploited in the wild. Patch this first, regardless of the base score.

baseline read

auto · not a community verdict

Real — exploited in the wild

CISA confirms active exploitation. Treat scanner hits as true positives unless your specific version or config is unaffected.

Based on CISA KEV

Confirm or dispute →

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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

Published

Embed this verdict
TruePositive verdict for CVE-2026-21509
Markdown
[![TruePositive verdict](https://www.truepositive.app/cve/CVE-2026-21509/badge.svg)](https://www.truepositive.app/cve/CVE-2026-21509)
HTML
<a href="https://www.truepositive.app/cve/CVE-2026-21509"><img src="https://www.truepositive.app/cve/CVE-2026-21509/badge.svg" alt="TruePositive verdict for CVE-2026-21509"></a>

Live badge that updates automatically as the community verdict changes.

Community ground truth

Be the first practitioner to weigh in

So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.

🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.

In your experience, is this finding real and exploitable?

awaiting field verdicts
Real, but not a risk here
Not a real issue

Curated baseline: TruePositive's read from public sources is Real & exploitable — a starting point, not a community verdict.

No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.

Field notes & remediation

Verdicts are the quick signal. Notes are the evidence and fixes behind them.

  • 0
    Field note · TruePositive EditorialCurated

    Microsoft Office Security Feature Bypass Vulnerability — Microsoft Office contains a security feature bypass vulnerability in which reliance on untrusted inputs in a security decision in Microsoft Office could allow an unauthorized attacker to bypass a security feature locally. Some of the impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version. Listed in the CISA KEV catalog (added 2026-01-26) — confirmed exploited in the wild, not theoretical. FIRST EPSS puts the chance of exploitation in the next 30 days at ~72%. Treat it as real and prioritize remediation over triage.

  • 0
    Remediation · TruePositive EditorialCurated

    Required action for Microsoft Office: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. CISA set a federal remediation due date of 2026-02-16. After patching, verify the vulnerable path is no longer reachable before closing the finding.

Add a field note or remediationoptional
Note type

What are you adding?

Markdown supported · minimum 20 characters.

Same weakness: CWE-807.