CVE-2026-61668

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (31st 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
8.1EG
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: 0.4%CVSS: 8.1Exploit: 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, WorkloadManagementSystem/Utilities/PilotWrapper.py pilotWrapperScript uses ssl._create_unverified_context to download the second-stage pilot.tar archive without TLS certificate verification and downloads the reference checksum through the same unvalidated channel. An attacker able to redirect or intercept a grid site's network traffic through DNS or routing manipulation can substitute both the executable pilot code and its checksum, causing arbitrary code to run in the pilot context with access to pilot proxy credentials. The fixed implementation validates the server certificate through system trust and X509_CERT_DIR or the grid certificate directory. This issue is fixed in versions 8.0.79, 9.0.22, and 9.1.10.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.4% × 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
0.4%
EPSS %ILE
31st
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 (7)

Auto-updated Sep 15, 2026
Patch available. Sources: github, github_commit, github_release.
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 b332c437d064 (DIRACGrid/DIRAC)

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

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

commit 92e2e26c63b9 (DIRACGrid/DIRAC)

Patch available: DIRACGrid/DIRAC v9.0.22 (contains commit 92e2e26c63b9)

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

commit 68029dfb5ddd (DIRACGrid/DIRAC)

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

https://github.com/DIRACGrid/DIRAC/commit/68029dfb5ddd8b1e4106851f8e37370aa80ac7ae
GitHub advisoryMentions a patch (unverified)

Pilot code downloaded over unverified HTTPS connection · Advisory · DIRACGrid/DIRAC · GitHub

https://github.com/DIRACGrid/DIRAC/security/advisories/GHSA-vg99-gr89-qhw9

Vendor Advisories for CVE-2026-61668(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.20.1 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(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 31× 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-13 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-13 13:22 UTCEG score recompute
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-12 15:50 UTCEG score recompute
  5. 2026-10-11 19:34 UTCEG score recompute
  6. 2026-10-11 16:49 UTCEG score recompute
  7. 2026-10-11 14:11 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-09-30 18:11 UTCEG score recompute
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-09-28 09:29 UTCEG score recompute
  22. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-09-24 10:04 UTCEG score recompute
  24. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  25. 2026-09-23 04:18 UTCEG score recompute
Show 10 more
  1. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  2. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  3. 2026-09-18 05:52 UTCEG score recompute
  4. 2026-09-17 18:15 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  6. 2026-09-15 18:36 UTCEG score recompute
  7. 2026-07-30 11:04 UTCEG score recompute
  8. 2026-07-26 11:52 UTCEG score recompute
  9. 2026-07-23 03:21 UTCEG score recompute
  10. 2026-07-13 19:08 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-61668?
CVE-2026-61668 is a high-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, WorkloadManagementSystem/Utilities/PilotWrapper.py pilotWrapperScript uses ssl.createunverifiedcontext to download the second-stage pilot.tar archive without TLS certificate…
When was the CVE record for CVE-2026-61668 published?
The CVE record for CVE-2026-61668 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-61668 actively exploited?
CVE-2026-61668 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61668?
CVE-2026-61668 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61668?
A fix for CVE-2026-61668 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61668 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-61668

Explore →

Is Your Infrastructure Affected by CVE-2026-61668?

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

Book a Demo →Browse All CVEs