| Version | Supported |
|---|---|
| 1.3.x | ✅ |
| 1.2.x | ✅ |
| < 1.2 | ❌ |
We take security vulnerabilities seriously. If you discover a security issue, please report it responsibly.
DO NOT create a public GitHub issue for security vulnerabilities.
Instead, please email: security@vouch-protocol.org
Or use GitHub's private vulnerability reporting:
- Go to the Security tab
- Click "Report a vulnerability"
- Fill out the form with details
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
| Action | Timeframe |
|---|---|
| Acknowledgment | 48 hours |
| Initial assessment | 1 week |
| Fix timeline provided | 2 weeks |
| Security advisory published | After fix is released |
- We follow responsible disclosure
- We will credit reporters (unless you prefer anonymity)
- We aim to fix critical vulnerabilities within 30 days
When using Vouch Protocol:
- Protect private keys - Never commit keys to source control
- Use environment variables - Store
VOUCH_PRIVATE_KEYsecurely - Rotate keys - Regenerate keys periodically
- Verify signatures - Always verify tokens server-side
- Check expiration - Tokens have short expiry for security
- Ed25519 keys: We use EdDSA (Ed25519) for cryptographic signing
- JWT structure: Tokens follow JWS compact serialization
- No symmetric keys: We only support asymmetric cryptography
Security updates are released as patch versions (e.g., 1.3.x).
Subscribe to GitHub releases for notifications.