VDB-340847 · CVE-2026-21219 · GCVE-0-2026-21219

Microsoft Windows SDK Inbox COM Objects use after free

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.4	$5k-$25k	0.00

Summaryinfo

A vulnerability has been found in Microsoft Windows SDK and classified as critical. Affected by this issue is some unknown functionality of the component Inbox COM Objects. The manipulation leads to use after free. This vulnerability is uniquely identified as CVE-2026-21219. Local access is required to approach this attack. No exploit exists. It is recommended to apply a patch to fix this issue.

Detailsinfo

A vulnerability was found in Microsoft Windows SDK (the affected version unknown). It has been rated as critical. This issue affects an unknown part of the component Inbox COM Objects. The manipulation with an unknown input leads to a use after free vulnerability. Using CWE to declare the problem leads to CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Use after free in Inbox COM Objects allows an unauthorized attacker to execute code locally.

The weakness was disclosed 01/13/2026 as confirmed security update guide (Website). It is possible to read the advisory at msrc.microsoft.com. The identification of this vulnerability is CVE-2026-21219. The exploitation is known to be difficult. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 02/09/2026).

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

Operating System

Vendor

Microsoft

Name

Windows SDK

License

commercial

Website

Vendor: https://www.microsoft.com/

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.0
VulDB Meta Temp Score: 6.4

VulDB Base Score: 7.0
VulDB Temp Score: 6.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

Vendor Base Score (Microsoft): 7.0
Vendor Vector (Microsoft): 🔒

CNA Base Score: 7.0
CNA Vector (Microsoft): 🔒

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Unproven

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔒
0-Day Time: 🔒
Exposure Time: 🔒

Timelineinfo

01/13/2026 VulDB entry created
01/13/2026 +0 days Advisory disclosed
01/13/2026 +0 days Countermeasure disclosed
02/09/2026 +27 days VulDB entry last update