We take security vulnerabilities seriously. If you discover a security issue, please report it responsibly.

Please DO NOT open a public GitHub issue for security vulnerabilities.

Instead, please email us at: security@headroomlabs.ai

Include the following information:

• Type of vulnerability (e.g., injection, data exposure, authentication bypass)
• Full path of the affected source file(s)
• Step-by-step instructions to reproduce the issue
• Proof-of-concept or exploit code (if possible)
• Impact assessment

1. Acknowledgment: We will acknowledge receipt within 48 hours
2. Assessment: We will assess the vulnerability and determine its severity
3. Updates: We will keep you informed of our progress
4. Resolution: We aim to resolve critical issues within 7 days
5. Credit: With your permission, we will credit you in the security advisory

When using Headroom:

1. API Keys: Never commit API keys. Use environment variables.
2. Proxy Exposure: Don't expose the proxy server to the public internet without authentication
3. Log Files: Be aware that request logs may contain sensitive information
4. Budget Limits: Set budget limits to prevent unexpected costs

The following are in scope for security reports:

• Headroom Python package (pip install headroom-ai)
• Headroom proxy server
• Official integrations (LangChain, Agno, Strands, LiteLLM, Vercel AI SDK, Anthropic/OpenAI SDK wrappers, MCP)

The following are out of scope:

• Third-party integrations not maintained by us
• Issues in dependencies (report these to the upstream project)
• Social engineering attacks

Headroom includes several security features:

• No credential storage: We never store or log API keys
• Passthrough mode: Sensitive content passes through unchanged by default
• Input validation: All inputs are validated before processing
• Safe defaults: Security-conscious defaults out of the box

Thank you for helping keep Headroom and its users safe!

The following public upstream advisories remain unresolved. They are included in uv.lock through optional extras; the presence of a package in that universal lockfile does not mean it is installed with every Headroom installation.

The crewai extra brings in ChromaDB through CrewAI. The locked ChromaDB 1.1.1 and the latest published version, 1.5.9, are affected by:

• GHSA-f4j7-r4q5-qw2c: pre-authentication code injection through model repository configuration.
• GHSA-36p7-vc44-83pf: code injection through model repository configuration with trust_remote_code.
• GHSA-2wm9-hf6c-p5cr: cross-tenant access to collection data.
• GHSA-xph7-9rjv-w5fr: missing resource-scope checks in SimpleRBACAuthorizationProvider.

There is no published patched release. The upstream authorization fix chroma-core/chroma#7602 is still open. Upgrading CrewAI alone also retains ChromaDB. Headroom's CrewAI integration wraps tools; it does not start a ChromaDB server or configure its authorization. Deployments that separately expose ChromaDB must not rely on its affected authorization for tenant isolation. Keep it inaccessible to untrusted clients and do not allow untrusted model repository or trust_remote_code configuration. These exposure restrictions are mitigations, not upstream fixes.

The voice-train extra includes Accelerate (locked at 1.12.0). GHSA-4j2p-28q2-5m79 describes path traversal and denial of service through unvalidated weight_map entries in sharded checkpoint indexes. Use only trusted checkpoints, including their index files and referenced shards, in training environments.

The advisory currently lists versions through 1.14.0, but an upgrade to 1.15.0 is not a verified fix: its checkpoint loader still joins index values to the checkpoint directory without containment or file-type validation. The proposed fixes #4070 and #4138 were closed without merging; the latter also explicitly leaves the named-pipe denial of service unfixed. Keep the alert open until a released fix covers both cases.

Dependabot ignores only the reviewed unpatched ranges (ChromaDB through 1.5.9 and Accelerate through 1.15.0). Later releases remain eligible for review. These update exceptions do not remediate the advisories or dismiss vulnerability alerts.