Clauster: Non-loopback deployments can serve the dashboard unauthenticated when auth.enabled is unset
- Product
- clauster
- Affected
- clauster <= 0.2.1
- Fixed in
- 0.2.2
Last verified against sources: October 26, 2026
Am I affected?
clauster: affected clauster <= 0.2.1. Fixed in 0.2.2.
- Check your version: run
pip show clauster. Versions <= 0.2.1 of clauster are affected. [1]
What to do now
- Upgrade to the fixed version: run
pip install --upgrade "clauster>=0.2.2"(first patched version 0.2.2). [1] - On any non-loopback deployment, set
auth.enabled: trueinclauster.yml(orCLAUSTER_AUTH_ENABLED=true) alongside your existingauth.password_required+ hash (or reverse-proxy) settings. [1] - Alternatively, bind to loopback only and reach it via an SSH tunnel or a trusted authenticating reverse proxy. [1]
General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.
What happened
- A Clauster instance bound to a non-loopback address can serve the entire dashboard and its API without any authentication if
auth.enabledis left at its default (false). [1] - The runtime auth guard enforces authentication only when
config.auth.enabledis true; when false it passes every request through unauthenticated. [1] - The config validator, for a non-loopback bind, required only one of
auth.password_required/auth.reverse_proxy.enabled/auth.allow_unauthenticated_network— notauth.enabled. [1] - Loopback (
127.0.0.1) deployments need no auth by design and are not affected. [1]
Impact
- An unauthenticated attacker with network access to the instance gains full control of the dashboard. [1]
- An unauthenticated attacker with network access to the instance can list projects, spawn/stop
claude remote-controlbridges in any project directory, editCLAUDE.md, read bridge logs, and (where configured) clone repositories. [1] - Because bridges run Claude Code against the host's project directories, this is effectively remote code execution in those projects. [1]
What was done
Sources
- GHSA-h4g2-xfmw-q2c9 — GitHub Advisory Database
Every statement above was checked against these sources before publishing. Spotted an error? Tell us and we will correct it with a dated note.
Share advisory brief with your team
Copy a plain-text summary for Slack, GitHub issues, or team security channels.
Clauster: Non-loopback deployments can serve the dashboard unauthenticated when auth.enabled is unset
Product: clauster | Affected: clauster <= 0.2.1 | Fixed in: 0.2.2
Summary: A Clauster instance bound to a non-loopback address can serve the entire dashboard and its API without any authentication if `auth.enabled` is left at its default (`false`).
Source & remediation on AgentArmorHQ: https://agentarmorhq.com/incidents/2026/07/ghsa-h4g2-xfmw-q2c9-clausterCorrections
Report an error or request a correction. We review requests within 5 business days and add a dated correction note.
Discussions for clauster
Ask questions or share configuration tips. Governed by our Community Rules & Terms.
No posts match this filter yet.
Be the first to ask a question or share a working tip.