Pardot Vulnerability Disclosure

Vulnerability disclosure

Salesforce Marketing Cloud Account Engagement (Pardot) runs a coordinated vulnerability disclosure program on Hackerone. A dedicated security contact is published.

Marketing AutomationB2B MarketingLead GenerationEmail MarketingSalesforceAccount Engagement
Program: Hackerone

Disclosure Policy

Security Contact

Contact
security@salesforce.com

Source

Vulnerability Disclosure

Raw ↑
generated: '2026-08-13'
method: searched
probe: true
source: https://security.salesforce.com/responsible-disclosure-policy/
note: Salesforce runs a published Responsible Disclosure Policy plus a HackerOne program at the corporate level;
  Account Engagement (Pardot) is in scope as a Salesforce cloud rather than having its own programme. Notably
  there is NO RFC 9116 security.txt on any Salesforce or Pardot host — the policy is discoverable only by browsing
  security.salesforce.com, so an automated scanner finds nothing. The provider-published contact address comes
  from SECURITY.md in the vendor's own GitHub org.
policy_url: https://security.salesforce.com/responsible-disclosure-policy/
policy_http_status: 200
contact: security@salesforce.com
contact_source: https://github.com/pardot/api-schemas/blob/master/SECURITY.md
security_txt:
  served: false
  probed:
  - pi.pardot.com
  - pi.demo.pardot.com
  - developer.salesforce.com
  - www.salesforce.com
  - trust.salesforce.com
  - login.salesforce.com
  status: 404
bug_bounty:
  platform: HackerOne
  url: https://hackerone.com/salesforce
  http_status: 200
safe_harbor:
  granted: true
  statement: Salesforce pledges not to initiate legal action against researchers for penetrating or attempting
    to penetrate its systems as long as they adhere to the policy.
testing_guidance: Conduct all vulnerability testing against a Trial or Developer Edition instance and use test
  or demo accounts. For Account Engagement that means the pi.demo.pardot.com host, not pi.pardot.com — see
  sandbox/pardot-sandbox.yml.
coordinated_disclosure: Salesforce notifies potentially impacted customers before public disclosure and CVE
  release.
researcher_credit: https://security.salesforce.com/security-research-contributors/
advisories: https://security.salesforce.com/
evidence:
- source: https://security.salesforce.com/responsible-disclosure-policy/
  kind: disclosure policy
  http_status: 200
- source: https://hackerone.com/salesforce
  kind: bug bounty program
  http_status: 200
- source: https://github.com/pardot/api-schemas/blob/master/SECURITY.md
  kind: repo security contact
  http_status: 200
- source: https://security.salesforce.com/
  kind: security advisories hub
  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/pardot-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.

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