53 lines (40 loc) · 1.83 KB

Security Policy

Supported Versions

Version	Supported
2.10.x	✅
< 2.10	❌

Reporting a Vulnerability

If you discover a security vulnerability, please report it responsibly:

Do NOT open a public GitHub issue for security vulnerabilities
Email: Open a private security advisory
Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (if any)

We will acknowledge receipt within 48 hours and provide a timeline for a fix.

Security Design

Authentication

All API endpoints (except /api/health) require Bearer token authentication
API keys are auto-generated with 256 bits of entropy (secrets.token_urlsafe(32))
Keys are stored locally at /config/.ha_cursor_agent_key

File System Access

All file operations are sandboxed to /config directory
Path traversal attempts are blocked (no .. allowed in paths)
Symlink resolution stays within the sandbox

Network

The agent listens on a single port (default 8099)
No outbound connections except to Home Assistant APIs
CORS is permissive by design (MCP clients are not browsers)

Git Versioning

Shadow git repository isolates versioning from user config
No remote git operations (push/pull) are performed
Commit history is bounded (max 30 commits by default)

Known Limitations

The agent has full read/write access to /config — this is by design for its functionality
Service calls can affect physical devices — always review AI actions before confirming
The MCP package runs with npx which downloads from npm — pin the version for production use:
```
npx -y @coolver/home-assistant-mcp@3.2.27
```