CVE-2026-61667

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.2% (67th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/100

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 computed (value × EchelonGraph’s weight)
Severity99% × 45%
The EG Score, 9.9 of 10.
Exploitation1.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.2%
EPSS %ILE
67th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 13, 2026

Last Modified

September 30, 2026

Advisory Details (10)

Auto-updated Oct 7, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

RCE in FileCatalog DatasetManager via SQL injection + eval · Advisory · DIRACGrid/DIRAC · GitHub

https://github.com/DIRACGrid/DIRAC/security/advisories/GHSA-m4m7-4cw8-62j6
GitHub release Patch Available

Release v9.1.10 (DIRACGrid/DIRAC)

Patch available: DIRACGrid/DIRAC v9.1.10

https://github.com/DIRACGrid/DIRAC/releases/tag/v9.1.10
GitHub release Patch Available

Release v9.0.22 (DIRACGrid/DIRAC)

Patch available: DIRACGrid/DIRAC v9.0.22

https://github.com/DIRACGrid/DIRAC/releases/tag/v9.0.22
GitHub release Patch Available

Release v8.0.79 (DIRACGrid/DIRAC)

Patch available: DIRACGrid/DIRAC v8.0.79

https://github.com/DIRACGrid/DIRAC/releases/tag/v8.0.79
GitHub commit Patch Available

commit fabf08a4a403 (DIRACGrid/DIRAC)

Patch available: DIRACGrid/DIRAC v8.0.79 (contains commit fabf08a4a403)

https://github.com/DIRACGrid/DIRAC/commit/fabf08a4a403fdd92d3445771528fa54b3ee902f
GitHub commit Patch Available

commit 6f6fe65f27b6 (DIRACGrid/DIRAC)

Patch available: DIRACGrid/DIRAC v9.0.22 (contains commit 6f6fe65f27b6)

https://github.com/DIRACGrid/DIRAC/commit/6f6fe65f27b6913916ef77a77a09918b94029c0a
GitHub commit Patch Available

commit 66cfc8bf1dc1 (DIRACGrid/DIRAC)

Patch available: DIRACGrid/DIRAC v9.1.10 (contains commit 66cfc8bf1dc1)

https://github.com/DIRACGrid/DIRAC/commit/66cfc8bf1dc13a6d38bf0c5654d5b551d76dce9b
GitHub commit Patch Available

commit 5a5def88d65a (DIRACGrid/DIRAC)

Patch available: DIRACGrid/DIRAC v9.0.22 (contains commit 5a5def88d65a)

https://github.com/DIRACGrid/DIRAC/commit/5a5def88d65a18c77af9f2900ffb5866d6489d62
GitHub commit Patch Available

commit 55ecbd729242 (DIRACGrid/DIRAC)

Patch available: DIRACGrid/DIRAC v9.1.10 (contains commit 55ecbd729242)

https://github.com/DIRACGrid/DIRAC/commit/55ecbd729242ddbe06251b57895873cc468f5a1a
GitHub commit Patch Available

commit 106f6efb40eb (DIRACGrid/DIRAC)

Patch available: DIRACGrid/DIRAC v8.0.79 (contains commit 106f6efb40eb)

https://github.com/DIRACGrid/DIRAC/commit/106f6efb40eb7318473fc09fc48083f1f864460a

Vendor 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)
PackageVulnerable rangeFix by version rangeDependents
dirac7.2.0 ... 9.1.9 (336 versions)
  • 6 up to 8.0.79: fixed in 8.0.79
  • 8.1.0a1 up to 9.0.22: fixed in 9.0.22
  • 9.1.0 up to 9.1.10: fixed in 9.1.10
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-14 09:04 UTCEG score recompute
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  3. 2026-10-13 05:53 UTCEG score recompute
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  5. 2026-10-12 15:50 UTCEG score recompute
  6. 2026-10-11 19:34 UTCEG score recompute
  7. 2026-10-11 16:49 UTCEG score recompute
  8. 2026-10-11 14:11 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  20. 2026-09-30 18:11 UTCEG score recompute
  21. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  23. 2026-09-28 09:29 UTCEG score recompute
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  25. 2026-09-24 10:04 UTCEG score recompute
Show 13 more
  1. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  2. 2026-09-23 04:18 UTCEG score recompute
  3. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  4. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  5. 2026-09-18 05:01 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  7. 2026-09-15 19:41 UTCEG score recompute
  8. 2026-09-15 18:48 UTCEG score recompute
  9. 2026-09-15 18:37 UTCEG score recompute
  10. 2026-07-30 09:31 UTCEG score recompute
  11. 2026-07-26 11:52 UTCEG score recompute
  12. 2026-07-23 03:21 UTCEG score recompute
  13. 2026-07-13 19:08 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-61667?
CVE-2026-61667 is a critical-severity vulnerability; its CVE record was published on July 13, 2026. 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…
When was the CVE record for CVE-2026-61667 published?
The CVE record for CVE-2026-61667 was published on July 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-61667 actively exploited?
CVE-2026-61667 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (67th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61667?
CVE-2026-61667 has a CVSS base score of 9.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61667?
A fix for CVE-2026-61667 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61667 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61667

Explore →

Is Your Infrastructure Affected by CVE-2026-61667?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs