Atomic Server: unauthenticated /setup invite grants Drive-wide write access (CVE-2026-69157)
Severity: critical · Patch status: unknown · Since 2026-07-06 · CVE-2026-69157
Atomic Server's bootstrap /setup invite (write=true, Drive root as target, usagesLeft=1) can be redeemed without authentication: GET /setup?public-key=<key makes the server create an Agent for that key with write access to the whole Drive, so an unclaimed instance can be taken over. The repository advisory GHSA-pfwx-xjp4-qxcj, published 2026-07-06 alongside atomic-server v0.40.3, describes this with reproduction steps, and NVD published CVE-2026-69157 on 2026-11-17 at CVSS 3.1 9.8 (CWE-306). The affected range is = 0.29.0 up to 0.40.2 per the repository advisory, although the global advisory record says <= 0.40.1. Release v0.40.3 (2026-07-06) fixed an inverted invite-expiry check and a race on usagesLeft; NVD states that no complete fixed version was verified, and the 0.41 prerelease line replaces the invite with tokens that need an authenticated agent. The advisory text serves as the public proof of concept. There is no CISA KEV entry, CISA's SSVC record shows exploitation none, and EPSS is 0.5%. Exposure is hard to size: crates.io shows 80,916 lifetime downloads (204 in the last 90 days) and the Docker Hub image joepmeneer/atomic-server 85,440 pulls, with its latest tag last pushed 2026-06-22, before the fix.
What to do
- Treat any atomic-server instance that was reachable before a fix as potentially compromised: audit Drive resources, agents and rights for agents you do not recognise
- Keep /setup unreachable from untrusted networks (firewall or reverse proxy) until a release with a verified redemption fix is available
- Check the version actually running: the Docker Hub latest tag of joepmeneer/atomic-server was last pushed 2026-06-22, before the v0.40.3 fix, so a pull does not imply the fix
- If you run a prerelease from the 0.41 line, confirm on your own instance that unauthenticated GET redemption of /setup is refused before relying on it
- Rotate server root keys and review commit history for unauthorised changes; the advisory states that write access can expose the server root key
Sources
All live incidents on Threat Watch