CVE-2026-61667 json
DIRAC: RCE in FileCatalog DatasetManager via SQL injection + eval
published 3mo ago modified yesterday also EUVD-2026-78896 , GHSA-m4m7-4cw8-62j6 , PYSEC-2026-3463
- cvss
- 9.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
DIRAC is an interware, meaning a software framework for distributed computing. Prior to versions 8.0.79, 9.0.22, and 9.1.10, DataManagementSystem/Service/FileCatalogHandler.py checkDataset forwards an authenticated caller-controlled datasets value to DatasetManager.py __checkDataset, 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 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.
Patch / fix
- pypi dirac 8.0.79, 9.0.22, 9.1.10
- diracgrid dirac 8.0.79, 9.0.22, 9.1.10
- github.com/DIRACGrid/DIRAC@106f6ef commit
- github.com/DIRACGrid/DIRAC@55ecbd7 commit
- github.com/DIRACGrid/DIRAC@5a5def8 commit
- github.com/DIRACGrid/DIRAC@66cfc8b commit
- github.com/DIRACGrid/DIRAC@6f6fe65 commit
- github.com/DIRACGrid/DIRAC@fabf08a commit
- github.com/DIRACGrid/DIRAC/releases/tag/v8.0.79 release
- github.com/DIRACGrid/DIRAC/releases/tag/v9.0.22 release
- github.com/DIRACGrid/DIRAC/releases/tag/v9.1.10 release
Is CVE-2026-61667 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last mo.
Exploit prediction
1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| OSV | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | dirac | >=6, <8.0.79 >=8.1.0a1, <9.0.22 >=9.1.0, <9.1.10 |
8.0.79 9.0.22 9.1.10 |
Affected products
- DIRACGrid DIRAC
Classification
References
-
github.com
/DIRACGrid/DIRAC/commit/106f6efb40eb7318473fc09fc48083f1f864460a
web
-
github.com
/DIRACGrid/DIRAC/commit/55ecbd729242ddbe06251b57895873cc468f5a1a
web
-
github.com
/DIRACGrid/DIRAC/commit/5a5def88d65a18c77af9f2900ffb5866d6489d62
web
-
github.com
/DIRACGrid/DIRAC/commit/66cfc8bf1dc13a6d38bf0c5654d5b551d76dce9b
web
-
github.com
/DIRACGrid/DIRAC/commit/6f6fe65f27b6913916ef77a77a09918b94029c0a
web
-
github.com
/DIRACGrid/DIRAC/commit/fabf08a4a403fdd92d3445771528fa54b3ee902f
web
-
github.com
/DIRACGrid/DIRAC/security/advisories/GHSA-m4m7-4cw8-62j6
web
-
github.com
/DIRACGrid/DIRAC/releases/tag/v8.0.79
web
-
github.com
/DIRACGrid/DIRAC/releases/tag/v9.0.22
web
-
github.com
/DIRACGrid/DIRAC/releases/tag/v9.1.10
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-61667
advisory
-
github.com
/DIRACGrid/DIRAC
package
-
github.com
/pypa/advisory-database/tree/main/vulns/dirac/PYSEC-2026-3463.yaml
web
-
pypi.org
/project/DIRAC/8.0.79
web
-
pypi.org
/project/DIRAC/9.0.22
web
-
pypi.org
/project/DIRAC/9.1.10
web
-
pypi.org
/project/dirac
package
-
github.com
/advisories/GHSA-m4m7-4cw8-62j6
advisory
Sources
- CVE List CVE-2026-61667
- GitHub Advisory GHSA-m4m7-4cw8-62j6
- NVD CVE-2026-61667
- OSV PYSEC-2026-3463
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.