Mailchimp · Vulnerability Disclosure

Mailchimp Vulnerability Disclosure

Vulnerability disclosure

Mailchimp publishes a vulnerability disclosure policy for reporting security issues. A machine-readable /.well-known/security.txt is served. A dedicated security contact is published.

CampaignsEmail MarketingMarketing AutomationNewslettersTransactional EmailAudience ManagementSMSE-CommerceWebhookMarketing Analytics

Program: security.txt present

Disclosure Policy

Policy

https://mailchimp.com/about/security/#Responsible_Disclosure

Security Contact

Contact

https://mailchimp.com/about/security/#Responsible_Disclosure

Source

Vulnerability Disclosure

generated: '2026-08-13'
method: searched
probe: true
source: https://mailchimp.com/.well-known/security.txt
checked: '2026-08-13'
policy:
  - https://mailchimp.com/about/security/#Responsible_Disclosure
contact:
  - https://mailchimp.com/about/security/#Responsible_Disclosure
bug_bounty:
  present: false
  detail: >-
    Mailchimp runs a responsible-disclosure program but explicitly states it is
    not a bug bounty: "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." Reports cover "any product, system, or asset belonging to
    Intuit."
disclosure_guidelines:
  - Share the security issue with Mailchimp before making it public.
  - Wait for notification that the vulnerability is resolved before disclosing to third parties.
  - Provide clear, concise reproduction steps and complete details, including a proof-of-concept URL.
security_txt:
  served: true
  url: https://mailchimp.com/.well-known/security.txt
  http_status: 200
  fields_present: [Contact]
  fields_missing: [Expires, Policy, Encryption, Preferred-Languages, Canonical]
  note: >-
    RFC 9116 requires an Expires field; Mailchimp's security.txt carries a single
    Contact line and nothing else, so it is served but not conformant.
  file: well-known/mailchimp-security.txt
evidence:
  - source: https://mailchimp.com/.well-known/security.txt
    kind: security.txt (live probe)
    http_status: 200
  - source: https://mailchimp.com/about/security/
    kind: responsible disclosure program page
    http_status: 200

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This security artifact

curl "https://apis.io/api/v1/security/mailchimp-vulnerability-disclosure"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.