| Version | Supported |
|---|---|
| v4.x | ✅ |
| v3.x | ❌ |
| v2.x | ✅ |
| v1.x | ❌ |
If you discover a security vulnerability in cmdguard, please report it privately.
Do not open a public issue.
Instead, send an email to lars@larsartmann.com with:
- A description of the vulnerability
- Steps to reproduce (if applicable)
- Potential impact
- Suggested fix (if you have one)
You can expect an initial response within 48 hours. If the vulnerability is confirmed, we will work with you to coordinate a fix and disclosure timeline.
When using cmdguard in production:
- Validate all inputs with
required:"true"orWithPreRunEhooks - Use
WithConfigValidationto enforce invariants after parsing - Keep dependencies up to date (run
go mod tidyregularly) - Avoid logging sensitive flag values (passwords, tokens) unless explicitly required
We follow a coordinated disclosure process:
- Reporter submits vulnerability privately
- Maintainers acknowledge receipt within 48 hours
- Maintainers investigate and develop a fix
- Fix is released in a patch version
- Public disclosure after users have had reasonable time to upgrade