CVE-2026-45579

CriticalCVSS 9.9

Published: 15/09/2026(UTC)Updated: 15/09/2026(UTC)Translated: 16/09/2026(UTC)NVD NIST

Summary

In DIRAC prior to versions 8.0.79, 9.0.22, and 9.1.10, the export_getRequestCountersWeb function in ReqManagerHandler.py passes an authenticated caller-controlled groupingAttribute to getRequestCountersWeb in RequestDB.py. An unrecognized value is resolved against the Request object and evaluated as Python code, allowing a crafted dunder attribute expression to reach operating-system functions and execute commands.

Risk Assessment

An authenticated attacker can execute commands as the account running DIRAC services, exposing dirac.cfg, database passwords, stored proxies, and tokens, fully compromising the DIRAC system and allowing alteration of local log evidence.

Recommendation

Upgrade DIRAC to version 8.0.79, 9.0.22, or 9.1.10 (or later). Consider rotating credentials (database passwords, tokens, proxies) if exploitation is suspected.

Other vulnerabilities in DIRAC

CVE-2026-61667Critical
In DIRAC prior to versions 8.0.79, 9.0.22, and 9.1.10, the checkDataset function in FileCatalogHandler.py forwards an authenticated caller-controlled datasets value to __checkDataset in DatasetManager.py, where datasetName is interpolated into an FC_MetaDatasets SQL query without parameterization. The injected query can control the returned MetaQuery value, which is passed to Python eval and permits command execution.

Original NVD description (English source)

DIRAC is an interware, meaning a software framework for distributed computing. Prior to versions 8.0.79, 9.0.22, and 9.1.10, the RequestManagementSystem/Service/ReqManagerHandler.py export_getRequestCountersWeb function passes an authenticated caller-controlled groupingAttribute to RequestManagementSystem/DB/RequestDB.py getRequestCountersWeb. An unrecognized value is resolved against the Request object and evaluated as Python code, allowing a crafted dunder attribute expression to reach operating-system functions and execute commands as the account running the DIRAC services. Successful exploitation can expose dirac.cfg, database passwords, stored proxies, and tokens, fully compromise the DIRAC system, and allow alteration of local log evidence. This issue is fixed in versions 8.0.79, 9.0.22, and 9.1.10.