Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for CVE-2026-61667.
Upgrade to ProDetect DIRAC FileCatalog DatasetManager SQL Injection to RCE (CVE-2026-61667) in Splunk
Detects exploitation attempts against DIRAC's FileCatalog DatasetManager component, where a SQL injection vulnerability (CWE-89) can be chained with unsafe eval() usage (CWE-95) to achieve remote code execution. Affects DIRAC versions >=6,<8.0.79; >=8.1.0a1,<9.0.22; >=9.1.0,<9.1.10. A public PoC exists (GHSA-m4m7-4cw8-62j6). Detection focuses on anomalous SQL error signatures, injection payload patterns in DatasetManager RPC calls, and subsequent process spawning from the DIRAC service process indicative of successful eval()-based code execution.
MITRE ATT&CK
SPL Detection Query
index=dirac OR sourcetype=dirac:filecatalog
| regex message="(?i)(union\s+select|or\s+'1'='1|__import__|os\.system|subprocess|eval\(|exec\(|drop\s+table|sleep\()"
| rex field=message "(?i)(?<matched_pattern>union select|or '1'='1|__import__|os\.system|subprocess|eval\(|exec\(|drop table|sleep\()"
| stats count by src_ip, dest_ip, matched_pattern, _time
| where count > 0
| sort -_timeSearches DIRAC FileCatalog service logs for SQL injection or Python code-execution payload indicators associated with the DatasetManager vulnerability.
Data Sources
Required Sourcetypes
False Positives & Tuning
- Internal QA test suites exercising DatasetManager with crafted edge-case strings
- Third-party integrations passing dataset names that coincidentally match regex patterns
- Security scanner traffic from authorized penetration tests
Other platforms for CVE-2026-61667
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 available with Pro.
- Test 1Simulate SQL injection payload against DatasetManager endpoint
Expected signal: HTTP request log entry on the DIRAC service showing the injected payload in the request body/message field.
- Test 2Simulate eval()-based code execution payload
Expected signal: Process creation event for a python/sh process spawned from the DIRAC service parent, with command line containing 'atomic_test_marker'.
- Test 3Simulate follow-on outbound connection from DIRAC service host
Expected signal: Network connection event from the DIRAC service account/process to an external or lab listener IP shortly after the injection attempt.
Unlock playbooks & atomic tests with Pro
Get the full detection package for CVE-2026-61667 — response playbook and atomic red team tests, plus investigation guidance and hunting queries.
df00tech Pro — £29/user/month