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.
CVE-2026-61667
This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.9
- EG Score
- 9.9(medium)
- EG Risk
- 45(Track)EG Risk 45/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity99% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 50%
- KEV
- Not listed
Published
July 13, 2026
Last Modified
September 15, 2026
Advisory Details (10)
Auto-updated Sep 15, 2026RCE in FileCatalog DatasetManager via SQL injection + eval · Advisory · DIRACGrid/DIRAC · GitHub
https://github.com/DIRACGrid/DIRAC/security/advisories/GHSA-m4m7-4cw8-62j6Release v9.1.10 (DIRACGrid/DIRAC)
Patch available: DIRACGrid/DIRAC v9.1.10
https://github.com/DIRACGrid/DIRAC/releases/tag/v9.1.10Release v9.0.22 (DIRACGrid/DIRAC)
Patch available: DIRACGrid/DIRAC v9.0.22
https://github.com/DIRACGrid/DIRAC/releases/tag/v9.0.22Release v8.0.79 (DIRACGrid/DIRAC)
Patch available: DIRACGrid/DIRAC v8.0.79
https://github.com/DIRACGrid/DIRAC/releases/tag/v8.0.79commit fabf08a4a403 (DIRACGrid/DIRAC)
Patch available: DIRACGrid/DIRAC v8.0.79 (contains commit fabf08a4a403)
https://github.com/DIRACGrid/DIRAC/commit/fabf08a4a403fdd92d3445771528fa54b3ee902fcommit 6f6fe65f27b6 (DIRACGrid/DIRAC)
Patch available: DIRACGrid/DIRAC v9.0.22 (contains commit 6f6fe65f27b6)
https://github.com/DIRACGrid/DIRAC/commit/6f6fe65f27b6913916ef77a77a09918b94029c0acommit 66cfc8bf1dc1 (DIRACGrid/DIRAC)
Patch available: DIRACGrid/DIRAC v9.1.10 (contains commit 66cfc8bf1dc1)
https://github.com/DIRACGrid/DIRAC/commit/66cfc8bf1dc13a6d38bf0c5654d5b551d76dce9bcommit 5a5def88d65a (DIRACGrid/DIRAC)
Patch available: DIRACGrid/DIRAC v9.0.22 (contains commit 5a5def88d65a)
https://github.com/DIRACGrid/DIRAC/commit/5a5def88d65a18c77af9f2900ffb5866d6489d62commit 55ecbd729242 (DIRACGrid/DIRAC)
Patch available: DIRACGrid/DIRAC v9.1.10 (contains commit 55ecbd729242)
https://github.com/DIRACGrid/DIRAC/commit/55ecbd729242ddbe06251b57895873cc468f5a1acommit 106f6efb40eb (DIRACGrid/DIRAC)
Patch available: DIRACGrid/DIRAC v8.0.79 (contains commit 106f6efb40eb)
https://github.com/DIRACGrid/DIRAC/commit/106f6efb40eb7318473fc09fc48083f1f864460aVendor Advisories for CVE-2026-61667(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| dirac | 7.2.0 ... 9.1.9 (336 versions) | 9.1.10 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 05:01 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-15 19:41 UTCEG score recompute
- 2026-09-15 18:48 UTCEG score recompute
- 2026-09-15 18:37 UTCEG score recompute
- 2026-07-30 09:31 UTCEG score recompute
- 2026-07-26 11:52 UTCEG score recompute
- 2026-07-23 03:21 UTCEG score recompute
- 2026-07-13 19:08 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-61667?
When was CVE-2026-61667 disclosed?
Is CVE-2026-61667 actively exploited?
What is the CVSS score of CVE-2026-61667?
How do I remediate CVE-2026-61667?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61667
Is Your Infrastructure Affected by CVE-2026-61667?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.