VORANT. Threat Intelligence Research Create a free account

Microsoft patches 200 flaws including 3 zero-days

Published Vorant ratingelevated vulnerability

Vorant's rating weighs the evidence in the report: confirmed exploitation, victims claimed, CVSS and EPSS, and how many sources agree. It rates the report, not your assets.

Microsoft's June 2026 Patch Tuesday addresses 200 vulnerabilities including three publicly disclosed zero-days: a CTFMON privilege escalation, HTTP/2 Bomb DoS, and BitLocker bypass.

Sourcebleepingcomputer.com — open the original

What to check

Applies to
The 16 CVEs named below. Whether you run an affected version is not assessed: check the versions the source lists.
Exploitation
No exploitation in the wild and no public exploit is recorded for the CVEs named.

Microsoft released its June 2026 Patch Tuesday updates fixing 200 security vulnerabilities, including 33 critical flaws. Three publicly disclosed zero-day vulnerabilities were patched, though none are known to have been actively exploited. The update addresses 28 remote code execution bugs, along with elevation of privilege, information disclosure, and denial of service flaws across Windows components, Office products, and enterprise services.

The three zero-days include CVE-2026-45586, a Windows CTFMON flaw allowing SYSTEM privilege escalation; CVE-2026-49160, the HTTP/2 Bomb denial-of-service vulnerability disclosed by Calif researchers that exploits HTTP/2 header compression to exhaust server memory; and CVE-2026-50507, the YellowKey BitLocker bypass disclosed by researcher Nightmare Eclipse. The BitLocker flaw allows local attackers with physical access to bypass encryption on TPM-only protected systems by booting into Windows Recovery Environment and accessing a command shell.

Critical patches include fixes for Windows Kerberos KDC remote code execution, Active Directory remote code execution, multiple Remote Desktop Client RCE flaws, and numerous Office product vulnerabilities. Microsoft introduced a new MaxHeadersCount registry setting to mitigate the HTTP/2 Bomb attack. The update excludes 360 Edge/Chromium flaws fixed earlier by Google and various Microsoft cloud service patches deployed throughout the month.

Mentioned in this report

Vulnerabilities CVE-2026-42985CVE-2026-42992CVE-2026-44799CVE-2026-44801CVE-2026-45586CVE-2026-45607CVE-2026-45641CVE-2026-45648CVE-2026-47288CVE-2026-47289CVE-2026-47291CVE-2026-47652CVE-2026-47654CVE-2026-48563CVE-2026-49160CVE-2026-50507

Detection guidance

Suspicious Child Process Spawned by CTFMON.EXE

ATT&CK T1068 · status experimental · needs windows process_creation logs · generated from the report, not run against telemetry

A behavioural hunt for the technique in general, not a signature for the CVEs this report names.

Detects ctfmon.exe (Windows CTF subsystem) spawning command interpreters or scripting hosts, consistent with exploitation of the CVE-2026-45586 CTF privilege-escalation flaw to reach SYSTEM. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.

title: Suspicious Child Process Spawned by CTFMON.EXE
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    ParentImage|endswith: \ctfmon.exe
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \pwsh.exe
    - \wscript.exe
    - \cscript.exe
    - \rundll32.exe
    - \mshta.exe
  filter:
    User|contains: SYSTEM
  condition: selection and not filter
falsepositives:
- Rare legitimate automation or accessibility tooling that hooks into the CTF input
  subsystem
level: high
tags:
- attack.t1068
- attack.privilege-escalation
id: cef209bd-355f-5cb5-bbd7-dcbb0696f033
status: experimental
author: Vorant

BitLocker Disabled or Removed via Manage-bde or Bcdedit

ATT&CK T1006 · status experimental · needs windows process_creation logs · generated from the report, not run against telemetry

A behavioural hunt for the technique in general, not a signature for the CVEs this report names.

Detects use of manage-bde or bcdedit to disable/decrypt BitLocker or alter boot configuration, consistent with local attackers exploiting the YellowKey WinRE command-shell bypass to access TPM-only protected volumes without a recovery key. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.

title: BitLocker Disabled or Removed via Manage-bde or Bcdedit
logsource:
  category: process_creation
  product: windows
detection:
  selection_managebde:
    Image|endswith: \manage-bde.exe
    CommandLine|contains:
    - -off
    - -disable
    - -forcerecovery
  selection_bcdedit:
    Image|endswith: \bcdedit.exe
    CommandLine|contains:
    - recoveryenabled
    - testsigning
    - nointegritychecks
  condition: 1 of selection_*
falsepositives:
- IT staff legitimately decommissioning or re-provisioning encrypted drives
- Authorized BitLocker recovery/troubleshooting performed by help desk with a valid
  recovery key
level: high
tags:
- attack.t1006
- attack.stealth
id: c36e36e3-3c2f-575a-a94a-14af36925d42
status: experimental
author: Vorant

HTTP/2 MaxHeadersCount Mitigation Value Tampered or Disabled

ATT&CK T1499 · status experimental · needs windows registry_set logs · generated from the report, not run against telemetry

A behavioural hunt for the technique in general, not a signature for the CVEs this report names.

Detects modification of the MaxHeadersCount registry value introduced to mitigate the HTTP/2 Bomb (CVE-2026-49160) header-compression denial-of-service, where the value is set to 0 or an unusually high limit, effectively disabling the protection. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.

title: HTTP/2 MaxHeadersCount Mitigation Value Tampered or Disabled
logsource:
  category: registry_set
  product: windows
detection:
  selection:
    TargetObject|contains: MaxHeadersCount
  suspicious_value:
    Details:
    - '0'
    - '0x00000000'
  condition: selection and suspicious_value
falsepositives:
- Administrator intentionally raising the header count limit for legitimate high-header-volume
  applications
level: medium
tags:
- attack.t1499
- attack.impact
id: e5251e26-9625-51af-a293-6394820454a1
status: experimental
author: Vorant

Behavioural rules are generated from public reporting — validate in your environment before deploying.

Source reporting: https://www.bleepingcomputer.com/news/microsoft/microsoft-june-2026-patch-tuesday-fixes-3-zero-day-200-flaws

Free public brief. The detections with Splunk SPL already written (plus Elastic and KQL where they apply) are in the app with a free account, no card. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them.

What this brief leaves out

This page is the free tier: the write-up, the severity, the names. In the app the same report carries its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply) and live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.

It sits in a corpus of 16,436 reports from 149 sources, 661 of them written in the last seven days, and it grows through the day.

A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.

Create a free account   What it costs