GHSA-SPECTERQA-001 (Critical): Command injection vulnerability in _check_preconditions affecting v0.2.0 and all earlier versions.
Workaround (immediate): Remove check_command from all product YAML files.
Fix: Upgrade to v0.2.1 when released.
See SECURITY_ADVISORY.md for full details.
| Version | Supported |
|---|---|
| 0.2.x | Yes (active) |
| 0.1.x | No |
| < 0.1 | No |
We provide security updates for the latest minor release. Older versions will not receive patches.
Please do not open a public GitHub issue for security vulnerabilities.
Instead, report vulnerabilities by emailing info@synctek.io. Include:
- A description of the vulnerability
- Steps to reproduce or a proof of concept
- The impact or severity as you understand it
- Your name/handle for attribution (optional)
| Action | Target |
|---|---|
| Acknowledgment of report | 48 hours |
| Initial assessment | 5 business days |
| Fix or mitigation released | 30 days |
We will keep you informed of our progress. If the issue is accepted, we will:
- Develop and test a fix privately
- Release a patched version
- Publish a security advisory on GitHub
- Credit the reporter (unless anonymity is requested)
The following are in scope for security reports:
- The
specterqaPython package (code insrc/) - CLI command injection or path traversal
- Unsafe handling of API keys or credentials
- Persona YAML injection leading to unintended behavior
The following are out of scope:
- Vulnerabilities in third-party dependencies (report those upstream)
- Issues requiring physical access to the machine
- Social engineering attacks
- Never commit your
.envfile or API keys to version control - Use environment variables or a secrets manager for
ANTHROPIC_API_KEY - Review persona YAML files from untrusted sources before running them
- Keep SpecterQA and its dependencies updated