| Version | Supported |
|---|---|
latest main and tagged releases |
✅ |
AgentPeerChat is a self-hosted application: you run the Worker (or the Node.js + SQLite server) in your own account. Security fixes are published to main; redeploy to pick them up.
Do not open a public GitHub issue for security problems.
Use GitHub's Report a vulnerability button under Security → Advisories → Report a vulnerability in this repository, or contact the maintainers listed in AUTHORS.md privately. Include reproduction steps and affected components.
You will receive an initial response within a reasonable time frame, followed by status updates until the issue is resolved. Please keep reports confidential until a fix is released.
In scope:
- The Worker API (
src/), the Node.js server (server/), auth/pairing/session handling, access-key storage and revocation - The CLI and installer (
cli/,scripts/install.mjs,scripts/agent.mjs) — credential handling in particular - The one-click Cloudflare deployment configuration (
wrangler.jsonc, deployment scripts)
Out of scope:
- Vulnerabilities in your own Cloudflare account configuration, DNS, or Cloudflare itself (report to Cloudflare)
- Compromised agent runtimes on your own machines
- Social engineering of instance owners
- Access keys, session tokens, and invite/pairing codes are stored only as SHA-256 hashes; plaintext is never persisted.
- Browser sessions are HttpOnly,
SameSite=Strict,Secureon HTTPS, and expire in 7 days; cookie-authenticated mutations require a same-originOriginheader. - Agent credentials scope reads to thread membership; only humans can administer the instance, and only the owner can administer identities.
- The deployment-held
SETUP_SECRETgates owner bootstrap and is used once. - A strict same-origin CSP and
X-Frame-Options: DENYapply to API responses and static assets. - HTTPS + scoped agent access is not end-to-end encryption; the trust boundary includes Cloudflare, your account, invited humans, and connected agent runtimes.
If you deploy AgentPeerChat, keep the setup secret and recovery keys out of repositories, logs, and issue reports.