This is the Trace Id: 3e85fe9c2c6f5cb319438275e053ec71
Skip to main content
MSRC

Secure research starts with responsible testing.

Microsoft Hyper-V Bounty Program

Partner with Microsoft to strengthen our products and services by identifying and reporting security vulnerabilities that could impact our customers. 
 

IMPORTANT: The Microsoft Bounty Program is subject to these terms and those outlined in the Microsoft Bounty Terms and ConditionsMicrosoft Bounty Legal Safe HarborRules of EngagementCoordinated Vulnerability Disclosure (CVD)Bounty Program Guidelines, and the Microsoft Bounty Program page.

PROGRAM DESCRIPTION

The Microsoft Hyper-V bounty program invites eligible researchers to find and submit vulnerabilities that reproduce in eligible product versions of Microsoft Hyper-V. Qualified submissions are eligible for bounty awards from $5,000 to $250,000 USD. This includes third-party and open-source components included in the service. Please note that qualifying reports must demonstrate a qualifying security impact on the specified service.

 

ELIGIBLE SUBMISSIONS

The goal of the Microsoft Bug Bounty program is to uncover significant technical vulnerabilities that have a direct and demonstrable impact on the security of our customers.

In addition to the eligibility requirements listed on the Bounty Program Guidelines page, vulnerability submissions must meet the following criteria to be eligible for bounty awards: 

 

1The classification of vulnerability severity levels varies by product. Products under the Hyper-V Bounty Program may be classified differently than those listed on the Microsoft Vulnerability Severity Classification for Windows.

 

We request researchers include the following information to help us quickly assess their submission:

 

Microsoft may accept or reject any submission at our sole discretion that we determine does not meet the above criteria. 


SCOPE

Vulnerabilities submitted in the following Product(s) are eligible under this bounty program

 

The Hyper-V Bounty Program is specifically aimed at finding vulnerabilities in Hyper-V that affect server hosting scenarios (such as Azure). Various Hyper-V client scenarios are covered under different bounties.

The Hyper-V bounty is focused on:

  • Components and features of Hyper-V that are used in server hosting scenarios (both traditional virtual machines and Hyper-V Isolation Containers).
  • The assumption that the Virtual Machine is on a separate VLAN than the host so there is no possibility to attack network services that are running on the host.
  • The assumption that the host will not be interacting with the Virtual Machine in a manner that is atypical when hosting servers. For example, the host will not use enhanced session mode to interact with the virtual machine.
  • If you have any questions regarding Hyper-V scope please reach out to hyperv-bounty@microsoft.com.

 

GETTING STARTED 

Please create a test account for security testing and probing. Please follow the Research Rules of Engagement to avoid harm to customer data, privacy, and service availability. If in doubt, please contact bounty@microsoft.com.

 

BOUNTY AWARDS

Bounty awards range from $5,000 up to $250,000 USD. Higher awards are possible, at Microsoft’s sole discretion, based on the severity and impact of the vulnerability and the quality of the submission. If a single submission is eligible for multiple awards, the submission will be awarded the single highest qualifying award.

Researchers who provide submissions that do not qualify for bounty awards may still be eligible for public acknowledgement if their submission leads to a vulnerability fix; they may also earn points in our Researcher Recognition Program to receive swag and secure a place on the Microsoft Most Valuable Researcher list.

A high-quality report provides the information necessary for an engineer to quickly reproduce, understand, and fix the issue. This typically includes a concise write-up containing any required background information, a description of the bug, and a proof of concept that reproduces without relying on a debugger for purposes such as suspending threads or modifying memory/code.

Sample high- and low-quality reports are available here.

 

Remote Code Execution

An eligible submission includes a RCE vulnerability in Microsoft Hyper-V that enables a guest virtual machine to compromise the hypervisor, escape from a guest virtual machine to the host, or escape from one guest virtual machine to another guest virtual machine.

Vulnerability TypeFunctioning ExploitReport QualityPayout range (USD)*
RCEYes
No
No
No
High
High
Medium
Low
$250,000
$200,000
$100,000
$50,000

Denial of Service and Information Disclosure

 
The vulnerability should result in one of the following:
  • Crashing the host machine, resulting in a non-transient denial of service condition
  • Causing a failure to start and/or stop VMs or the host, requiring manual intervention or rendering the host unusable for 15 minutes or more
  • Gaining sensitive information from the host machine or another guest
Vulnerability TypeReport QualityPayout range (USD)*
DOSHigh
Medium
Low
$15,000
$10,000
$5,000
Info DisclosureHigh
Medium
Low
$25,000
$15,000
$5,000

OUT-OF-SCOPE SUBMISSIONS AND VULNERABILITIES

Microsoft is happy to receive and review every submission on a case-by-case basis, but some submission and vulnerability types may not qualify for bounty award.

If your submission is evaluated as out-of-scope for this individual bounty program, it may still qualify for an award under the Standard Award Policy.

Here are some of the common low-severity or out-of-scope issues that typically do not earn bounty awards:

  • Publicly-disclosed vulnerabilities which have already been reported to Microsoft or are already known to the wider security community.
  • Vulnerabilities that can only be triggered by an attacker running code on the host.
  • Vulnerabilities that require the Hyper-V VM to send network traffic to host listeners. For example, this includes, without limitation attacks against the hosts TCP, SMB or RPC stack. Attacks against the virtualized network stack (for example, this includes, without limitation VMSwitch) are in scope.
  • Vulnerabilities in Legacy Network Adapter (Generation 1) and Fibre Channel Adapter. 
  • Vulnerabilities that can only be triggered when the guest is connected to via the RDP protocol. For example, this includes, without limitation RDP or Enhanced Session Mode.
  • Vulnerabilities in deprecated features. For example, this includes, without limitation, RemoteFX.
  • Vulnerabilities that cannot be triggered when Hyper-V is used to host traditional virtual machines (Generation 1 or 2) or Hyper-V isolation containers.
  • Vulnerabilities that require the following configuration changes to be made by a Hyper-V administrator:
    • Enabling an undocumented feature or undocumented configuration. For example, this includes, without limitation enabling an experimental feature or using an undocumented configuration that intentionally puts the system in an insecure state.
    • Enabling a feature/configuration that is only intended for out-of-scope scenarios. This includes, without limitation enabling a feature only intended for use with WDAG on a traditional VM.
  • Vulnerabilities based on third parties that do not demonstrate a qualifying security impact on the specified service, this includes this includes, without limitation Docker and Kubernetes.
  • Training, documentation, samples, and community forum sites related to Microsoft Hyper-V bounty program products and services are out-of-scope for bounty awards.

Microsoft reserves the right to reject any submission that we determine, at our sole discretion, falls into any of these categories of vulnerabilities even if otherwise eligible for a bounty.

 

ADDITIONAL INFORMATION

For additional information please see our FAQ.

 

REVISION HISTORY

  • May 31, 2017: Program Launch.
  • December 7, 2018: Revision History added.
  • January 22, 2019: Added Hyper-V isolation containers to the bounty scope.
  • March 15, 2019: Added examples to Tier 2 definition and specified third party code vulnerabilities as out-of-scope.
  • April 13, 2020: Removed Remotefx® from bounty scope.
  • February 23, 2021: Changed RCE vulnerabilities that only occur when all virtual processors are stopped to Tier 3 unless a working exploit is demonstrated.
  • November 8, 2021: Clarified in-scope products and clarified out-of-scope issues.
  • January 25, 2022: Consolidated Scope and Bounty Awards, and added researcher guidance.
  • June 11, 2025: Added details to the Bounty Program Awards section for submissions that rely on debugger intervention.
  • August 25, 2025: Updated Denial of Service and Information Disclosure requirements.
  • December 11, 2025: Updated hyperlinks and standardized language.