DIRAC · CVE-2026-61667 · Package
FIX → 9.1.10 · 8.0.79 +1
DIRAC's FileCatalog DatasetManager builds a SQL query with an f-string and passes the result into Python's eval. An authenticated user can inject SQL to control that result and run arbitrary commands on the server.
first public Jul 13, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Exposure requires running a DIRAC FileCatalog service that accepts requests from authenticated users, since the flaw sits in the DatasetManager reached through checkDataset. Installations that only use DIRAC client tools without the FileCatalog service, or that run versions at or above the fixed releases, are not affected. Teams running DIRAC grid infrastructure should look at the FileCatalog handler in their deployment.
Not affected if client-only, no-filecatalog-service, patched-version
Who cares dirac, filecatalog, grid-computing, python
pip show DIRAC8.0.79, 9.0.22, 9.1.10The FileCatalog DatasetManager runs a query on the database and passes the result to eval. The SQL query contains an injection vulnerability which allows an authenticated user to control the parameter returned to the eval resulting in remote code execution.
The FileCatalog checkDataset function passes its datasets argument directly to the backend DB handler: https://github.com/DIRACGrid/DIRAC/blob/f7e0a3ac153315030fb3520e8ca747f013758967/src/DIRAC/DataManagementSystem/Service/FileCatalogHandler.py#L591-L593
Which in turn passes it to the __checkDataset function: https://github.com/DIRACGrid/DIRAC/blob/f7e0a3ac153315030fb3520e8ca747f013758967/src/DIRAC/DataManagementSystem/DB/FileCatalogComponents/DatasetManager/DatasetManager.py#L390
This uses an f-string to create a query without escaping, resulting in an SQL injection: https://github.com/DIRACGrid/DIRAC/blob/f7e0a3ac153315030fb3520e8ca747f013758967/src/DIRAC/DataManagementSystem/DB/FileCatalogComponents/DatasetManager/DatasetManager.py#L400-L402
The result (which is user controllable due to the SQL injection) is passed into eval almost immediately on return, leading to code execution: https://github.com/DIRACGrid/DIRAC/blob/f7e0a3ac153315030fb3520e8ca747f013758967/src/DIRAC/DataManagementSystem/DB/FileCatalogComponents/DatasetManager/DatasetManager.py#L409
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Upgrade to 9.1.10 · 8.0.79 +1
8.0.79: move to 8.0.799.0.22: move to 9.0.229.1.10: move to 9.1.10There are other functions in the same file which use a similar pattern and would likely be exploitable in a similar way.
This allows any authenticated user to run commands on the server, which allows a full compromise of the DIRAC system (they can read the local dirac.cfg, get database passwords and export all stored proxies and tokens). If local logging is used, they can also remove evidence of the exploit from the log.
https://pypi.org/project/DIRAC/8.0.79/ https://pypi.org/project/DIRAC/9.0.22/ https://pypi.org/project/DIRAC/9.1.10/
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.