Product security · Responsible disclosure

Help keep the prpl ecosystem secure.

Have you identified a potential security vulnerability affecting prplWare? We welcome good-faith reports from security researchers and the wider community.

A connected open-source ecosystem

↗Applications & servicesOpen ecosystem and third-party software
◈Platform · prplWare / prplOSCarrier-grade software stack
⌁Connectivity & managementprplMesh · APIs · lifecycle management
▦Linux · SoC · hardwareKernel, drivers and vendor components
✳ Security is a shared responsibility

Security through collaboration and openness

Clear, confidential reporting helps the prpl Foundation Security Incident Response Group (SIRG) assess issues and coordinate appropriate remediation.

↗

Report privately

Send your report directly to the security contact. Please avoid sharing vulnerability details publicly before coordination with the SIRG.

⌑

Encrypt sensitive material

OpenPGP encryption is strongly encouraged for technical details, proof-of-concept material, logs or other sensitive attachments.

◎

Coordinate disclosure

The SIRG will review the report and work with relevant parties to handle the issue and communicate as appropriate.

Report a vulnerability

Include enough detail to help the security team understand, reproduce and assess the potential issue.

Security contact

Reports are monitored by appointed members of the prpl Foundation SIRG.

Important: Do not put sensitive technical details, credentials, personal data, proof-of-concept code or confidential logs in the email subject. Send sensitive material only in the encrypted message body or encrypted attachments.

Encrypted reporting

OpenPGP public key

Encrypt sensitive reports for the SIRG Chair using the public key below.

Identity
prpl Foundation SIRG Chair
[email protected]

Fingerprint

E637 E339 864B 33F8
4560 CD69 8F5E 8DFD
3B55 C404

↓ Download the public key (.asc)

What to include in your report

Helpful reports are specific and reproducible. Share what you can safely provide; do not delay reporting because one detail is missing.

  • A clear description of the suspected vulnerability
  • Affected project, component and version
  • Configuration, repository or environment details
  • Steps to reproduce the issue
  • Potential security impact and relevant threat assumptions
  • Logs, screenshots, patches or proof-of-concept material, where useful
  • Possible mitigation or remediation suggestions, if known
Protect confidential information. Credentials, personal data, confidential logs and exploit details should be included only in the encrypted message body or encrypted attachments—not in the subject line.

Coordinated vulnerability disclosure

The prpl Foundation aims to give relevant parties a reasonable opportunity to investigate and address a reported vulnerability before public disclosure.

What happens next?

The SIRG reviews the report, follows the internal Security Incident Response Process and communicates with the reporter as appropriate. Please keep the report confidential while coordination is ongoing.

Rewards and bug bounty

The prpl Foundation does not currently operate a bug bounty program. Reporting a vulnerability does not imply eligibility for a financial reward.

This page is also referenced by the prpl Foundation security.txt file.

Close