Detect Rucio Unauthenticated Admin Impersonation via SSH Challenge Tokens (CVE-2026-100397) in Sumo Logic CSE
Detects exploitation of CVE-2026-100397, an authentication bypass in Rucio. The function validate_auth_token in lib/rucio/core/authentication.py does not distinguish short-lived SSH challenge tokens from real authentication tokens, because both are stored in the same token table. Challenge tokens are generated from an account name supplied in the X-Rucio-Account header without prior authentication, so an unauthenticated attacker can request a challenge token for any account, including an administrative one, and present it as a valid auth token. The attacker requests a token at /auth/ssh_challenge_token, receives it in the X-Rucio-SSH-Challenge-Token header, then sends it as X-Rucio-Auth-Token to other API endpoints as that account. This is tracked as CWE-287 and CWE-305. Detection focuses on authentication requests to the Rucio SSH auth endpoints, anomalous account values in X-Rucio-Account headers, and subsequent privileged administrative API calls (account creation, identity addition, RSE management) performed with freshly minted tokens from unexpected source IPs.
MITRE ATT&CK
Sumo Detection Query
// df00tech DF00-5ce6ae0814 · https://df00tech.com/detections/CVE-2026-100397 · licence: https://df00tech.com/detections/licence
_sourceCategory=rucio/access ("/auth/ssh" OR "/auth/ssh_sign" OR "/auth/ssh_challenge_token")
| parse "* - - [*] \"* * *\" * *" as src_ip, ts, method, uri, proto, status, bytes nodrop
| where status = "200"
| where uri matches /\/auth\/ssh/
| timeslice 10m
| count as auth_count by _timeslice, src_ip, uri
| where auth_count >= 3 Detects repeated successful authentication to the Rucio SSH challenge-token endpoints within a 10-minute window per source IP in Sumo Logic.
Data Sources
Required Tables
False Positives & Tuning
- Legitimate high-frequency grid clients
- Health-check probes
- Service nodes authenticating multiple accounts
Other platforms for CVE-2026-100397
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.
- Test 1 Rucio SSH auth endpoint burst
Expected signal: Five HTTP GET requests to /auth/ssh_challenge_token with X-Rucio-Account: root from one source IP in the web/proxy access logs.
- Test 2 Account-cycling against SSH auth endpoint
Expected signal: Multiple /auth/ssh_challenge_token requests with differing X-Rucio-Account values from one source IP.
- Test 3 Privileged API call after SSH auth
Expected signal: An /auth/ssh_challenge_token request followed within minutes by a POST /accounts/* from the same source IP.
References (7)
- https://github.com/rucio/rucio/security/advisories/GHSA-x585-4vv8-2mh2
- https://github.com/advisories/GHSA-x585-4vv8-2mh2
- https://github.com/rucio/rucio/commit/4d4a58571ba853f3a55aef16ad9eb0944fce7483
- https://github.com/rucio/rucio/releases/tag/35.9.1
- https://github.com/rucio/rucio/releases/tag/38.6.1
- https://github.com/rucio/rucio/releases/tag/40.4.2
- https://github.com/rucio/rucio/releases/tag/41.1.1
Response Playbook
Triage
- Confirm the Rucio server version from the deployment (pip show rucio / container image tag) and compare against affected ranges (>=1.14.0.post1 <35.9.1, >=36.0.0rc1 <38.6.1, >=39.0.0rc1 <40.4.2, >=41.0.0rc1 <41.1.1).
- Review the Rucio auth server logs for source IP(s) hitting /auth/ssh_challenge_token and identify which account identity was requested via the X-Rucio-Account header.
- Correlate any admin-scoped token issuance with subsequent privileged API calls (account/identity/RSE creation or modification) within the same session window.
- Determine whether the source IP belongs to a known grid service, monitoring system, or an unrecognized/external host.
Containment
- Expire or revoke all active Rucio auth tokens to force re-authentication and kill any impersonated admin sessions.
- Block the offending source IP(s) at the reverse proxy/WAF and temporarily disable the SSH authentication method on the Rucio server until patched.
- Upgrade Rucio to a fixed release (35.9.1, 38.6.1, 40.4.2, or 41.1.1 and later) immediately.
Evidence Collection
- Preserve the Rucio httpd/gunicorn access and error logs covering the suspected exploitation window.
- Export the Rucio tokens table and identities/account_map tables to capture issued tokens and any attacker-added SSH identities.
- Snapshot the Rucio database and capture auth server configuration showing enabled authentication methods.
Escalation Criteria
- !An admin-scoped token was issued to a source IP not matching any known administrator or service account.
- !New Rucio accounts, identities, or RSEs were created or modified following a suspicious SSH authentication, indicating successful privilege abuse.
Investigation Guide
Forensic Artifacts
- >
Rucio tokens table rows with admin-scoped accounts and unexpected issuance IPs - >
New or modified rows in the identities and account_map tables (attacker-added SSH keys) - >
Rucio httpd access log entries to /auth/ssh_challenge_token with X-Rucio-Account headers
Tuning Guidance
Build an allowlist of source IPs for known grid service clients (FTS, DIRAC, data management daemons) and monitoring probes, then exclude them from the volume thresholds. Lower the auth_count threshold in low-traffic environments and raise it where legitimate automated clients authenticate frequently. Prioritize any event where an admin-scoped token is followed by write operations to /accounts, /identities, or /rses endpoints.
Hunting Queries
Enumerate all historical Rucio SSH authentication attempts grouped by source IP and requested account to baseline normal vs anomalous callers.
// df00tech DF00-5ce6ae0814 · https://df00tech.com/detections/CVE-2026-100397 · licence: https://df00tech.com/detections/licence
W3CIISLog | where csUriStem has "/auth/ssh" | summarize by cIP, csUsername, bin(TimeGenerated, 1h) | order by TimeGenerated desc ``` df00tech DF00-5ce6ae0814 · https://df00tech.com/detections/CVE-2026-100397 · licence: https://df00tech.com/detections/licence ```
index=web uri_path="/auth/ssh*" | stats count values(rucio_account) by src_ip | sort - count Atomic Red Team Tests
Simulate repeated requests to the Rucio SSH challenge-token endpoint from a single host to trigger the volume-based detection.
Command
for i in $(seq 1 5); do curl -s -o /dev/null -w '%{http_code}\n' -H 'X-Rucio-Account: root' https://rucio-lab.example.org/auth/ssh_challenge_token; done Cleanup
echo 'No persistent changes; clear test logs if desired' Expected Telemetry
Five HTTP GET requests to /auth/ssh_challenge_token with X-Rucio-Account: root from one source IP in the web/proxy access logs.
Expected Detection
KQL/SPL volume rule fires on auth_count >= 3 from a single source IP.
Issue auth requests cycling multiple account identities to trigger the multi-account branch of the detection.
Command
for acct in root admin ddmadmin svcuser; do curl -s -o /dev/null -H "X-Rucio-Account: $acct" https://rucio-lab.example.org/auth/ssh_challenge_token; done Cleanup
echo 'No cleanup required' Expected Telemetry
Multiple /auth/ssh_challenge_token requests with differing X-Rucio-Account values from one source IP.
Expected Detection
Rule fires on distinct_accounts > 1 for a single source IP.
Simulate a successful SSH challenge-token request followed by a privileged account-creation API call to trigger the EQL sequence correlation.
Command
curl -s -o /dev/null -H 'X-Rucio-Account: root' https://rucio-lab.example.org/auth/ssh_challenge_token; curl -s -o /dev/null -X POST -H 'X-Rucio-Auth-Token: TESTTOKEN' https://rucio-lab.example.org/accounts/attacker Cleanup
curl -s -X DELETE -H 'X-Rucio-Auth-Token: TESTTOKEN' https://rucio-lab.example.org/accounts/attacker || true Expected Telemetry
An /auth/ssh_challenge_token request followed within minutes by a POST /accounts/* from the same source IP.
Expected Detection
Elastic EQL sequence rule correlates the auth event with the subsequent privileged admin API call.