Please do not report security vulnerabilities through public GitHub issues.
If you discover a security vulnerability in liblloyal, please report it privately:
- Email: Send details to security@lloyal.ai
- Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)
We will acknowledge your email within 48 hours and provide a detailed response within 7 days.
Security issues in liblloyal include:
- Memory safety: Buffer overflows, use-after-free, null pointer dereferences
- API misuse: Operations that could cause crashes or undefined behavior
- Resource exhaustion: Unbounded allocations, infinite loops
- Integer overflows: In position calculations, buffer sizing, etc.
The following are not considered security issues:
- Bugs in llama.cpp itself (report to llama.cpp project)
- Model-level vulnerabilities (prompt injection, jailbreaks)
- Performance issues without security impact
- Compilation warnings without runtime impact
We provide security updates for:
- Current release (latest stable version)
- Previous minor version (for 90 days after new release)
- We aim to patch critical vulnerabilities within 30 days
- We will coordinate disclosure timing with the reporter
- Credit will be given to reporters (unless anonymity requested)
When using liblloyal:
- Validate inputs: Always check model paths, token arrays, and parameters
- Resource limits: Set appropriate context sizes and batch limits
- Error handling: Handle all exceptions and check return values
- Memory monitoring: Track KV cache size and state memory usage
None reported to date.