LiveActive security incident?Get immediate response
CVE Record

CVE-2026-21530: Windows Rich Text Edit Elevation of Privilege Vulnerability

Double free in Windows Rich Text Edit allows an authorized attacker to elevate privileges locally.

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A memory-management flaw in Microsoft’s Rich Text Edit component could let a logged-in attacker gain higher privileges after user interaction. It is not remotely exploitable by itself, but successful exploitation could enable broad control over data and system functions.

Executive priority

Schedule remediation through the normal security-update cycle, accelerating higher-risk shared or privileged systems. The moderate score and exploitation prerequisites reduce emergency urgency, but potential full confidentiality, integrity, and availability impact makes deferral inappropriate.

Technical view

CVE-2026-21530 is a CWE-415 double-free vulnerability with CVSS 3.1 score 6.7. Exploitation requires local access, low privileges, high attack complexity, and user interaction. A successful attack can compromise confidentiality, integrity, and availability without crossing a security scope boundary.

Likely exposure

Exposure includes the listed Microsoft 365 and Office editions, Windows 10 and 11 versions, and Windows Server 2012 through 2016 installations. Prioritize systems where untrusted users can sign in or users routinely handle untrusted rich-text content.

Exploitation context

The bundle does not establish active exploitation, and the CVE is not marked as included in KEV. Exploitation requires an authorized local attacker and user interaction, which limits initial access but makes the flaw relevant after account compromise or insider access.

Researcher notes

The supplied record identifies the double-free weakness but provides no root-cause detail, attack chain, proof of concept, indicators, or patched build numbers. Treat claims beyond the stated local, authorized, user-interaction-dependent privilege escalation as unverified and consult Microsoft’s advisory for product-specific servicing data.

Mitigation direction

  • Review Microsoft’s advisory and deploy the applicable security updates for every affected product.
  • Prioritize shared workstations, administrative endpoints, servers, and systems accessible to lower-trust users.
  • Apply least privilege and restrict unnecessary local access while updates are pending.
  • Follow Microsoft guidance for any product-specific mitigations or servicing requirements.

Validation and detection

  • Inventory installed Windows and Office editions and compare them with the affected product list.
  • Confirm applicable Microsoft security updates are installed successfully across managed endpoints and servers.
  • Re-scan updated assets and investigate systems that remain vulnerable or cannot receive updates.
  • Review endpoint security telemetry for suspicious local privilege changes; no CVE-specific indicators were provided.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-415: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-21530 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.7CVSS 3.1MediumCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C0.85.9microsoft

Vulnerability scoring details

Base CVSS 3.1 score

6.7Medium
CVSS 3.1 vector shape for CVE-2026-21530Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftMicrosoft 365 Apps for Enterprise16.0.1Listed
MicrosoftMicrosoft Office 201616.0.0Listed
MicrosoftMicrosoft Office 201919.0.0Listed
MicrosoftMicrosoft Office LTSC 202116.0.1Listed
MicrosoftMicrosoft Office LTSC 202416.0.0Listed
MicrosoftWindows 10 Version 160710.0.14393.0Listed
MicrosoftWindows 10 Version 180910.0.17763.0Listed
MicrosoftWindows 10 Version 21H210.0.19044.0Listed
MicrosoftWindows 10 Version 22H210.0.19045.0Listed
MicrosoftWindows 11 version 23H210.0.22631.0Listed
MicrosoftWindows 11 Version 23H210.0.22631.0Listed
MicrosoftWindows 11 Version 24H210.0.26100.0Listed
MicrosoftWindows 11 Version 25H210.0.26200.0Listed
MicrosoftWindows 11 version 26H110.0.28000.0Listed
MicrosoftWindows Server 20126.2.9200.0Listed
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0Listed
MicrosoftWindows Server 2012 R26.3.9600.0Listed
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0Listed
MicrosoftWindows Server 201610.0.14393.0Listed
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0Listed
MicrosoftWindows Server 201910.0.17763.0Listed
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0Listed
MicrosoftWindows Server 202210.0.20348.0Listed
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)10.0.25398.0Listed
MicrosoftWindows Server 202510.0.26100.0Listed
MicrosoftWindows Server 2025 (Server Core installation)10.0.26100.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-415 · source CWE mapping

Double Free

Double Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.