- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 7
- 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 by email
- https://mailchimp.com/about/security
- Partial safe harbor
- Some legal protection; read the terms.
- Replies within 3 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
This program isn’t intended to represent a public bug bounty program and we make no offers of reward or compensation for submitting potential issues.
- Response
-
Within 3 days
Mailchimp will review and promptly acknowledge any submitted issue within three business days of submission through its web form, found here: Responsible Disclosure Form
- Safe harbor
-
Partial
By following these guidelines and responsibly disclosing any security weaknesses directly to Intuit, we agree not to pursue legal action against you. Mailchimp reserves its legal rights in the event of noncompliance with program guidelines.
Summarised with AI from the company's policy, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
7 assets you may test, 4 excluded.
APIs 3
- https://mailchimp.com/developer/guides/transactional-api-quick-start No bounty
- Marketing API No bounty
- Transactional API No bounty
Domains 3
- mailchimp.com
- mailchimp.com/developer/marketing/guides/quick-start No bounty
- mailchimp.com/resources/free-marketing-features-overview No bounty
Products and areas 1
- any product, system, or asset belonging to Intuit
Out of scope (4)
- Any form of denial of service (DoS) attack
- Phishing
- Physical security assessments
- Social engineering
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Mailchimp's policy. "We" in these lines means the program, not this site.
While testing
-
Share the security issue with us before making it public (e.g., on message boards, mailing lists, or other forums).
-
Wait until we provide you notification that the vulnerability has been resolved before you disclose it to third parties.
-
Provide a clear, concise description of the steps needed to reproduce any vulnerability you submit.
-
Provide the complete details related to the security issue, including proof-of-concept (POC) URL, as well as the details of the system(s) where tests have been conducted.
-
Don’t cause harm to Mailchimp, Intuit, its customers, shareholders, partners or employees.
-
Don’t engage in any act that may cause an outage or stop any of Mailchimp’s services.
-
Don’t engage in illegal activities or any acts that violate any international laws or regulations, or federal or state laws or regulations.
-
Don’t store, share, compromise or destroy any Mailchimp data or customer data while conducting research activities.
-
If personally identifiable information (PII) is encountered, you are required to stop and immediately notify Mailchimp.
-
Don’t conduct fraudulent activity or complete fraudulent financial transactions as part of your research.
Not accepted
-
Phishing
-
Social engineering
-
Physical security assessments
-
Any form of denial of service (DoS) attack
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 5 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.