# CVE-2026-50507 — Microsoft Windows 10 Version 1607

> As of 2026-06-23, CVE-2026-50507 is a MEDIUM-severity vulnerability in Microsoft Windows 10 Version 1607, CVSS v3.1 6.8, EPSS 5.0% (91.1th percentile). Threadlinqs Intelligence links 2 tracked threat campaigns to CVE-2026-50507, most recently “CVE-2026-50661: Windows BitLocker Security Feature Bypass 0-Day”.

**Last updated:** 2026-06-23

## What is CVE-2026-50507?

Protection mechanism failure in Windows BitLocker allows an unauthorized attacker to bypass a security feature with a physical attack.

The record classifies CVE-2026-50507 under weakness class [CWE-306](https://cwe.mitre.org/data/definitions/306.html). Its CVSS v3 base vector states that the flaw requires physical access to the device, needs no prior authentication, needs no user interaction, and has high impact on confidentiality, integrity, availability. 12 affected-product entries are recorded, across 1 vendor, listed below. The identifier was first published 95 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 6.8 — MEDIUM (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C`)
- **EPSS (FIRST):** 5.0% probability of exploitation in the next 30 days, higher than 91.1% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 9/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-06-09, last modified 2026-06-23

## Is CVE-2026-50507 being exploited?

Weaponised exploit code for CVE-2026-50507 is publicly available. 1 public proof-of-concept repository is tracked for this identifier.

- [HORKimhab/CVE-2026-50507](https://github.com/HORKimhab/CVE-2026-50507) (github)

## Affected products and versions

- **Microsoft**: Windows 10 Version 1607, Windows 10 Version 1809, Windows 10 Version 21H2, Windows 10 Version 22H2, Windows 11 version 23H2, Windows 11 Version 23H2, Windows 11 Version 24H2, Windows 11 Version 25H2, Windows 11 version 26H1, Windows Server 2012 R2, Windows Server 2012 R2 (Server Core installation), Windows Server 2016

## How to fix CVE-2026-50507

No vendor patch reference has been recorded for CVE-2026-50507 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-50507

2 tracked threats in the Threadlinqs corpus reference CVE-2026-50507, either in the campaign’s CVE list or as an indicator on the campaign record.

- [CVE-2026-50661: Windows BitLocker Security Feature Bypass 0-Day](https://intel.threadlinqs.com/threat/TL-2026-1346) — MEDIUM · 2026-07-15
- [Microsoft June 2026 Patch Tuesday — 198+ CVEs Including CVE-2026-49160 (HTTP.sys 'HTTP/2 Bomb' DoS), CVE-2026-50507 (BitLocker 'YellowKey' Bypass) and CVE-2026-45586 (Collaborative Translation Framework EoP)](https://intel.threadlinqs.com/threat/TL-2026-0732) — HIGH · 2026-06-09

## Sources

Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on 2026-06-25.

**Vendor advisory and patch**

- [msrc.microsoft.com — vendor advisory](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50507)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-50507
Full detection coverage and IOCs for threats exploiting CVE-2026-50507 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp