Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for CVE-2026-45579.
Upgrade to ProDetect DIRAC RequestManager eval() Remote Code Execution (CVE-2026-45579) in Google Chronicle
Detects exploitation attempts and successful compromise of DIRAC's RequestManager component via CVE-2026-45579, a CWE-95 (Eval Injection) vulnerability where untrusted RPC input passed to RequestManager is evaluated via Python's eval() function, resulting in unauthenticated or low-privilege remote code execution. Affected DIRAC (pip package) versions are >=6,<8.0.79, >=8.1.0a1,<9.0.22, and >=9.1.0,<9.1.10. A public PoC exists (GHSA-9jpv-c7p4-997x). Detection focuses on anomalous eval-triggering payloads sent to DIRAC RequestManager RPC/DISET endpoints, resulting child process spawns from DIRAC service processes, and post-exploitation artifacts consistent with grid/HPC computing infrastructure compromise.
MITRE ATT&CK
YARA-L Detection Query
rule dirac_requestmanager_eval_rce_cve_2026_45579 {
meta:
author = "df00tech"
description = "Detects process spawns from DIRAC RequestManager consistent with CVE-2026-45579 eval injection RCE"
severity = "CRITICAL"
cve = "CVE-2026-45579"
events:
$proc.metadata.event_type = "PROCESS_LAUNCH"
$proc.principal.process.parent_process.command_line = /(?i)(RequestManager|dirac-service|dirac-request)/
$proc.principal.process.command_line = /(?i)(eval\(|__import__|os\.system|subprocess|socket\.socket|\/bin\/sh|base64)/
condition:
$proc
}Chronicle YARA-L rule detecting process launch events where a process with a DIRAC RequestManager/service parent command line spawns a child process containing eval-injection indicators, mapping to CVE-2026-45579 exploitation.
Data Sources
Required Tables
False Positives & Tuning
- Legitimate administrative use of eval() for DIRAC diagnostics
- Test/CI automation invoking RequestManager with benign payloads
- Unrelated processes sharing substring matches in command lines
Other platforms for CVE-2026-45579
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 DIRAC RequestManager eval() RCE via crafted RPC payload
Expected signal: Process creation event showing python3 (DIRAC RequestManager service) spawning /bin/sh -c "id > /tmp/dirac_poc_out" or equivalent child process with eval-injection command-line markers
- Test 2Simulate reverse shell spawned from DIRAC service process
Expected signal: Bash process with /dev/tcp redirection spawned by a process whose parent command line references RequestManager/dirac-service, plus an outbound TCP connection on port 4444
- Test 3Simulate malicious eval() injection payload execution on Windows lab host
Expected signal: DeviceProcessEvents entry showing python.exe spawning cmd.exe/whoami with a parent command line simulation referencing RequestManager, writing output to a temp file
Unlock playbooks & atomic tests with Pro
Get the full detection package for CVE-2026-45579 — response playbook and atomic red team tests, plus investigation guidance and hunting queries.
df00tech Pro — £29/user/month