Twilio's Vulnerability Disclosure Policy

Vulnerability Disclosure Philosophy

Twilio believes effective disclosure of security vulnerabilities requires mutual trust, respect, transparency and common good between Twilio and Security Researchers. Together, our vigilant expertise promotes the continued security and privacy of Twilio customers, products, and services.

Security Researchers

Twilio accepts vulnerability reports from all sources such as independent security researchers, industry partners, vendors, customers and consultants. Twilio defines a security vulnerability as an unintended weakness or exposure that could be used to compromise the integrity, availability or confidentiality of our products and services.

Scope

This policy applies to any digital assets owned, operated, or maintained by Twilio, including public facing websites.

Our Commitment to Researchers

  • Trust. We maintain trust and confidentiality in our professional exchanges with security researchers.
  • Respect. We treat all researchers with respect and recognize your contribution for keeping our customers safe and secure.
  • Transparency. We will work with you to validate and remediate reported vulnerabilities in accordance with our commitment to security and privacy.
  • Common Good. We investigate and remediate issues in a manner consistent with protecting the safety and security of those potentially affected by a reported vulnerability.

What We Ask of Researchers

  • Trust. We request that you communicate about potential vulnerabilities in a responsible manner, providing sufficient time and information for our team to validate and address potential issues.
  • Respect. We request that researchers make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing.
  • Transparency. We request that researchers provide the technical details and background necessary for our team to identify and validate reported issues, using the form below.
  • Common Good. We request that researchers act for the common good, protecting user privacy and security by refraining from publicly disclosing unverified vulnerabilities until our team has had time to validate and address reported issues.

Vulnerability Reporting

Twilio recommends that security researchers share the details of any suspected vulnerabilities across any asset owned, controlled, or operated by Twilio (or that would reasonably impact the security of Twilio and our users) using the web form below. The Twilio Security team will acknowledge receipt of each vulnerability report, conduct a thorough investigation, and then take appropriate action for resolution.

Bug Bounty Program

For those interested in earning potential rewards for their security expertise, please submit your report through our Bug Bounty Program.

Submission form

All fields are required unless marked optional.

Summary title

Help us get an idea of what this vulnerability is about.

Target

Select the vulnerable target

Targets that are not explicitly in scope may not be eligible for acceptance.

Technical severity

The Vulnerability Rating Taxonomy is the baseline guide used for classifying technical severity.

Select or search for a vulnerability type

Vulnerability details

For example: https://secure.server.com/some/path/file.php

Describe the vulnerability and its impact.

Provide a proof of concept or replication steps.

Maximum 25,000 characters.

Attachments (optional)

Attach proof-of-concept scripts, screenshots, screen recordings, etc.

You can attach up to 20 files. Please keep individual upload size under 400MiB.

You can embed attachments (.jpg/.gif/.png, smaller than 5MB) into the Markdown fields. You can copy the embed code using the ‘Copy as Markdown’ button.

    Email

    By providing your email address you can claim your submission on bugcrowd.com.

    Confirmation

    Confirm your submission is accurate and adheres to Bugcrowd’s terms & conditions.