Cribl’s Vulnerability Disclosure Program
For Cribl, building relationships with our customers and partners on a foundation of trust is of the highest importance. As the Data Engine for IT and Security, security and privacy are always top priorities.
Cribl appreciates our partnership with the security community and welcomes feedback from security researchers and the general public to help improve our security. If you believe you have discovered a vulnerability, privacy issue, exposed data, or other security issues in any of our assets, we want to hear from you.
Cribl discloses vulnerabilities coordinated through our vulnerability disclosure program to ensure users receive complete, accurate, and timely information about vulnerabilities and mitigations.
Cribl’s vulnerability disclosure program follows Bugcrowd's Standard Disclosure Terms, which outline expectations for researchers and participating organizations. Researchers participating in this program agree to those terms.
When a reported vulnerability is confirmed, Cribl will investigate, develop a fix or mitigation, and coordinate disclosure with the reporting researcher when applicable. Cribl may assign a CVE identifier to eligible vulnerabilities within the scope of our VDP and publish a security advisory on our Trust Portal describing the issue, affected versions, and remediation guidance.
Cribl publishes vulnerability details only after a fix or mitigation is available. Disclosure timelines may vary depending on the complexity and severity of the issue, the availability of remediation, and coordination requirements with third parties. Cribl reserves the right to determine the timing and content of public disclosures to balance transparency with the safety of customers and the broader ecosystem.
Researchers who report vulnerabilities through this program may be publicly acknowledged in the advisory or CVE record unless they request to remain anonymous.
Before submitting a report, please review our vulnerability disclosure policy which can be found below. Please use the form on the adjacent tab to submit your report.
This vulnerability policy (“Policy”) outlines the steps for reporting vulnerabilities to us, what we expect, and what you can expect from us.
Systems in Scope
This Policy applies to any digital assets owned, operated, or maintained by Cribl that are not explicitly in the Out of Scope section below. We are specifically interested in reports affecting the following domains:
Systems Out of Scope
Cribl Cloud integrates with Auth0 for authentication. Auth0 is NOT in scope for testing. The following URLs are explicitly out of scope for security testing:
Assets or other equipment owned or operated by third parties.
Vulnerabilities discovered or suspected in out-of-scope systems should be reported to the appropriate vendor or applicable authority.
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 and provided written authorization for disclosure.
Vulnerability Reporting
Cribl recommends that security researchers share the details of any suspected vulnerabilities across any asset owned, controlled, or operated by Cribl (or that would reasonably impact the security of Cribl and our users) using the web form on the adjacent tab. The Cribl Security team will acknowledge receipt of each vulnerability report, conduct a thorough investigation, and then take appropriate action for resolution.