Do not open public issues for security vulnerabilities.
If you discover a security issue in OpenConnect, please report it privately:
- Email: [email protected]
- Subject:
[SECURITY] OpenConnect - <brief description>
Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact assessment
- Suggested fix (if any)
You will receive a response within 48 hours. We aim to resolve critical vulnerabilities within 7 days.
OpenConnect includes the following security measures:
- httpOnly cookies — JWT tokens are XSS-resistant (never in localStorage)
- CORS lockdown — Restricted to known origins (app + hub domains)
- CSP headers — Strict Content Security Policy
- Selector sanitization — Blocks
javascript:,data:,<scriptin selectors - Rate limiting — Registration and login rate limiting per IP
- Anti-gaming — Daily caps, 24h account age, email verification requirements
- Input validation — Pydantic models, max lengths, URL scheme validation
- Docker hardening — Non-root user,
NoNewPrivileges,ProtectSystem=strict
- Selectors defined in connector JSON are executed in a headless Chromium context. Maliciously crafted selectors cannot escape the Playwright sandbox.
- The execution engine creates a fresh BrowserContext per execution — no shared state between user sessions.
Direct dependencies are pinned in server/requirements.txt. We recommend
running pip audit in your deployment pipeline:
pip install pip-audit
pip audit -r server/requirements.txt