| Version | Supported |
|---|---|
| Latest release | Yes |
| Previous minor | Security fixes only |
| Older | No |
Do NOT open a public GitHub issue for security vulnerabilities.
Please report security issues by emailing the maintainers directly or using GitHub Private Vulnerability Reporting (Security tab → Report a vulnerability).
- Description of the vulnerability and affected component
- Steps to reproduce or proof-of-concept
- Potential impact assessment
- Your suggested fix (optional)
| Stage | Target |
|---|---|
| Acknowledgement | Within 72 hours |
| Initial assessment | Within 7 days |
| Fix or mitigation | Within 90 days (critical: 30 days) |
| Public disclosure | After fix is released |
In scope:
internal/api/— Admin UI CSRF, authentication bypassinternal/secrets/— Credential storage and retrievalinternal/adapters/— Injection via protocol payloads- Windows service privilege escalation
- Log output containing plaintext secrets
Out of scope:
- Issues requiring physical access to the machine
- Denial of service against the local loopback interface
- Vulnerabilities in third-party dependencies not yet patched upstream
- The Admin UI binds to
127.0.0.1:7201only (loopback, not LAN-accessible by default). - All write endpoints require a CSRF token (11 endpoints protected).
- Credentials are stored via Windows DPAPI / Credential Manager.
- Log output is scrubbed by
internal/logging/redact.gobefore writing. - No Goodreads API key is stored — the bridge operates via the Calibre plugin only.