| Version | Supported |
|---|---|
| 1.x | ✅ |
| < 1.0 | ❌ |
Please do not report security vulnerabilities through public GitHub issues.
If you discover a security vulnerability in x402-cli, please report it privately:
-
GitHub Security Advisories (Preferred): Go to Security Advisories and create a new advisory.
-
Email: Send details to security@port402.com
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Any suggested fixes (optional)
- Acknowledgment: Within 48 hours
- Initial Assessment: Within 7 days
- Resolution: Depends on severity, typically 30-90 days
- We will acknowledge your report within 48 hours
- We will investigate and keep you informed of progress
- We will credit you in the release notes (unless you prefer anonymity)
- We will coordinate disclosure timing with you
x402-cli handles sensitive data including:
- Private keys (via
--keystoreor--walletflags) - Payment signatures (EIP-712 typed data)
- Never share your private key or keystore password
- Use dedicated test wallets for testing
- Keep your keystore files secure with appropriate file permissions
- Review payment amounts before confirming (
--dry-runflag) - Use
--max-amountflag to set spending limits
The following are not considered vulnerabilities:
- Issues in third-party dependencies (report to upstream)
- Social engineering attacks
- Physical attacks requiring local access
- Denial of service via excessive API calls