We actively support and provide security updates for the following versions:
| Version | Supported |
|---|---|
| 1.x | Supported |
| < 1.0 | Not supported |
Security fixes go into the latest 1.x release. For the Revit and Python versions that are built and tested, see the table below and the deprecation policy.
| Component | Supported | Notes |
|---|---|---|
| Revit | 2024, 2025, 2026, 2027 | Built in CI for every year |
| Python | 3.11, 3.12, 3.13 | Tested on Windows in CI. Linux (3.12) is experimental. |
DO NOT open public GitHub issues for security vulnerabilities.
Use GitHub's private security advisory feature:
- Navigate to the repository's Security tab
- Click "Report a vulnerability"
- Provide detailed information
- Description: Clear description of the vulnerability
- Steps to Reproduce: Detailed steps to demonstrate the issue
- Impact Assessment: What an attacker could achieve
- Affected Versions: Which versions are vulnerable
- Suggested Fix (optional): Your recommendations
- Acknowledgment: Within 48 hours
- Initial Triage: Within 7 days
- Fix Development:
- Critical: Within 7 days
- High: Within 30 days
- Medium: Within 90 days
We follow coordinated disclosure:
- Private report received
- Fix developed and tested
- Patched version released
- Public disclosure after 30 days
- Keep the bridges on localhost. They bind to
127.0.0.1only. Do not expose them through a reverse proxy or port forward. There is no HTTPS, OAuth or rate limiting on the local bridges; they rely on the localhost boundary and, in the default Revit mode, a session token (see docs/security.md). - Keep approval on. Leave
MCP_REVIT_APPROVAL_MODEat its default (required). Settingautoturns the approval check off. - Limit the workspace. Set
MCP_REVIT_WORKSPACE_DIRandMCP_REVIT_ALLOWED_DIRECTORIESto the folders you need. - Check the logs. The server writes
audit.log(see docs/logging-and-audit.md) and the Revit add-in writes%APPDATA%\AECModelBridge\Logs\bridge.jsonl. Restrict access to both. - Update regularly. Apply security releases within 30 days.
- Do not give an AI client a shell on the account you approve plans with. The panel authenticates a local process, not a person.
- Tool arguments are validated against schemas before they reach a provider.
- Keep secrets out of code; use environment variables or a keyring.
- Audit entries and tool responses are redacted for secrets and local paths.
Before relying on a deployment:
- Bridges bind to
127.0.0.1only and are not behind a port forward - Workspace directories are limited to the folders you need
-
MCP_REVIT_APPROVAL_MODEis notauto - Access to
audit.logandbridge.jsonlis restricted - No AI client has a shell on the account used to approve plans
Nothing in this product has run in a live Revit session yet; see docs/release-checklist.md.
Full guide: docs/security.md