Millennium Challenge Corporation
Vulnerability disclosure program on Self-hosted mcc.gov
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 6
- Public CVEs
- 0
- Last change
- No changes yet
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report through their form
- bugcrowd.com/mcc-vdp
- Full safe harbor
- Good-faith research is authorised; no legal action.
- Replies within 5 days
- As the policy promises.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What the company's own policy page says it pays.
This program does not pay cash rewards.
- Pays cash
-
No
MCC will provide no monetary award, intention to advertise or give public credit to Researchers for identification of vulnerabilities.
- Response
-
Within 5 days
If you share contact information (Reporter Contact), we will acknowledge receipt of your report within five (5) business days of the report's receipt.
- Safe harbor
-
Full
If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and MCC will not recommend or pursue legal action related to your research.
- Hall of fame
-
No
MCC will provide no monetary award, intention to advertise or give public credit to Researchers for identification of vulnerabilities.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
6 assets you may test, 3 excluded.
Domains 3
- mcc.gov
- mcc.icpsr.umich.edu
- mcctest.gov
Wildcard domains 3
- mcc.icpsr.umich.edu and all subdomains of mcc.icpsr.umich.edu
- www.mcc.gov , and all subdomains of mcc.gov
- www.mcctest.gov and all subdomains of mcctest.gov
Out of scope (3)
- Any services not explicitly listed above
- non-federal systems from our vendors
- third-party applications, websites, or services that integrate with or link to or from MCC systems
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Millennium Challenge Corporation's policy. "We" in these lines means the program, not this site.
While testing
-
Notify us as soon as possible after you discover a real or potential security issue.
-
Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
-
Only use exploits to the extent necessary to confirm a vulnerability’s presence.
-
Do not use an exploit to compromise or exfiltrate data, establish command line access and/or persistence, or use the exploit to pivot to other systems.
-
Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
-
Do not submit a high volume of low-quality reports.
-
Engage in physical testing of facilities or resources.
-
Engage in social engineering.
-
Send unsolicited electronic mail to MCC users, including “phishing” messages.
-
Execute or attempt to execute a denial of service (DoS) attack, a distributed denial of service (DDoS) attack, attempt any type of resource exhaustion attack on MCC networks or systems.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 6 hours ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.