How severe is GHSA-h4g2-xfmw-q2c9?

No CVSS score has been assigned to GHSA-h4g2-xfmw-q2c9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h4g2-xfmw-q2c9?

GHSA-h4g2-xfmw-q2c9 affects the following packages: clauster (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-h4g2-xfmw-q2c9?

Update clauster to 0.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h4g2-xfmw-q2c9 is resolved across your whole dependency graph.

How do I detect GHSA-h4g2-xfmw-q2c9 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for clauster. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-h4g2-xfmw-q2c9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-h4g2-xfmw-q2c9?

O3 pinpoints whether GHSA-h4g2-xfmw-q2c9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-h4g2-xfmw-q2c9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-h4g2-xfmw-q2c9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-h4g2-xfmw-q2c9 published, and has it been updated?

GHSA-h4g2-xfmw-q2c9 was published on July 10, 2026 and was last updated on July 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-h4g2-xfmw-q2c9

Clauster: Non-loopback deployments can serve the dashboard unauthenticated when auth.enabled is unset

Published

Jul 10, 2026

Updated

Jul 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐍clauster

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Summary

A Clauster instance bound to a non-loopback address (e.g. 0.0.0.0 or a LAN IP) can serve the entire dashboard and its API without any authentication — even when the operator has configured a password — if auth.enabled is left at its default (false). The operator believes the instance is password-protected; in reality every request is served unauthenticated.

Impact

An unauthenticated attacker with network access to the instance gains full control of the dashboard: list projects, spawn/stop claude remote-control bridges in any project directory, edit CLAUDE.md, read bridge logs, and (where configured) clone repositories. Because bridges run Claude Code against the host's project directories, this is effectively remote code execution in those projects.

Loopback (127.0.0.1) deployments need no auth by design and are not affected.

Affected configurations

All released versions (≤ 0.2.1) where all of the following hold:

host is a non-loopback address, and
auth.password_required: true and/or auth.reverse_proxy.enabled: true is set, and
auth.enabled is left at its default false.

Docker deployments are affected: the image binds 0.0.0.0, and the previously-documented docker run command did not set auth.enabled.

Root cause

Two layers checked different flags:

The runtime auth guard enforces authentication only when config.auth.enabled is true; when false it passes every request through unauthenticated.
The config validator, for a non-loopback bind, required only one of auth.password_required / auth.reverse_proxy.enabled / auth.allow_unauthenticated_network — not auth.enabled. So a config with a password but enabled=false validated, started, and enforced nothing.

Proof of concept

With host: 0.0.0.0, auth.password_required: true, a valid auth.password_hash, and auth.enabled unset:

curl http://<host>:7621/api/instances

returns 200 with the full instance list and no credentials. Setting auth.enabled: true returns 401.

Patches

An upcoming patch release makes the config validator fail closed: a non-loopback bind is refused unless authentication is actually enforced — auth.enabled: true together with auth.password_required (+ a hash) or auth.reverse_proxy.enabled, or the explicit auth.allow_unauthenticated_network opt-out. The README, clauster.yml.example, and Docker docs were corrected to match.

Workaround

On any non-loopback deployment, set auth.enabled: true in clauster.yml (or CLAUSTER_AUTH_ENABLED=true) alongside your existing auth.password_required + hash (or reverse-proxy) settings. Alternatively, bind to loopback only and reach it via an SSH tunnel or a trusted authenticating reverse proxy.

Credit

Found during an internal security review.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`clauster`	all versions	0.2.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for clauster. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update clauster to 0.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h4g2-xfmw-q2c9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-h4g2-xfmw-q2c9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-h4g2-xfmw-q2c9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary A Clauster instance bound to a **non-loopback** address (e.g. `0.0.0.0` or a LAN IP) can serve the entire dashboard and its API **without any authentication** — even when the operator has configured a password — if `auth.enabled` is left at its default (`false`). The operator believes the instance is password-protected; in reality every request is served unauthenticated. ### Impact An unauthenticated attacker with network access to the instance gains full control of the dashboard: list projects, **spawn/stop `claude remote-control` bridges in any project directory**, edit `CLAUDE.

O3 Security · Impact-Aware SCA

Is GHSA-h4g2-xfmw-q2c9 in your dependencies?

O3 detects GHSA-h4g2-xfmw-q2c9 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works