DIRACGrid DIRAC up to 8.0.78/9.0.21/9.1.9 Pilot Wrapper PilotWrapper.py certificate validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.89 |
Summary
A vulnerability classified as problematic has been found in DIRACGrid DIRAC up to 8.0.78/9.0.21/9.1.9. This affects an unknown part of the file WorkloadManagementSystem/Utilities/PilotWrapper.py of the component Pilot Wrapper. The manipulation leads to certificate validation. This vulnerability is uniquely identified as CVE-2026-61668. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in DIRACGrid DIRAC up to 8.0.78/9.0.21/9.1.9. This issue affects some unknown processing of the file WorkloadManagementSystem/Utilities/PilotWrapper.py of the component Pilot Wrapper. The manipulation with an unknown input leads to a certificate validation vulnerability. Using CWE to declare the problem leads to CWE-295. The product does not validate, or incorrectly validates, a certificate. Impacted is integrity. The summary by CVE is:
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.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-61668 since 07/10/2026. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1587.003 for this issue.
Upgrading to version 8.0.79, 9.0.22 or 9.1.10 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 8.0.0
- 8.0.1
- 8.0.2
- 8.0.3
- 8.0.4
- 8.0.5
- 8.0.6
- 8.0.7
- 8.0.8
- 8.0.9
- 8.0.10
- 8.0.11
- 8.0.12
- 8.0.13
- 8.0.14
- 8.0.15
- 8.0.16
- 8.0.17
- 8.0.18
- 8.0.19
- 8.0.20
- 8.0.21
- 8.0.22
- 8.0.23
- 8.0.24
- 8.0.25
- 8.0.26
- 8.0.27
- 8.0.28
- 8.0.29
- 8.0.30
- 8.0.31
- 8.0.32
- 8.0.33
- 8.0.34
- 8.0.35
- 8.0.36
- 8.0.37
- 8.0.38
- 8.0.39
- 8.0.40
- 8.0.41
- 8.0.42
- 8.0.43
- 8.0.44
- 8.0.45
- 8.0.46
- 8.0.47
- 8.0.48
- 8.0.49
- 8.0.50
- 8.0.51
- 8.0.52
- 8.0.53
- 8.0.54
- 8.0.55
- 8.0.56
- 8.0.57
- 8.0.58
- 8.0.59
- 8.0.60
- 8.0.61
- 8.0.62
- 8.0.63
- 8.0.64
- 8.0.65
- 8.0.66
- 8.0.67
- 8.0.68
- 8.0.69
- 8.0.70
- 8.0.71
- 8.0.72
- 8.0.73
- 8.0.74
- 8.0.75
- 8.0.76
- 8.0.77
- 8.0.78
- 9.0.0
- 9.0.1
- 9.0.2
- 9.0.3
- 9.0.4
- 9.0.5
- 9.0.6
- 9.0.7
- 9.0.8
- 9.0.9
- 9.0.10
- 9.0.11
- 9.0.12
- 9.0.13
- 9.0.14
- 9.0.15
- 9.0.16
- 9.0.17
- 9.0.18
- 9.0.19
- 9.0.20
- 9.0.21
- 9.1.0
- 9.1.1
- 9.1.2
- 9.1.3
- 9.1.4
- 9.1.5
- 9.1.6
- 9.1.7
- 9.1.8
- 9.1.9
Website
- Product: https://github.com/DIRACGrid/DIRAC/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.1
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Certificate validationCWE: CWE-295 / CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: DIRAC 8.0.79/9.0.22/9.1.10
Timeline
07/10/2026 CVE reserved09/15/2026 Advisory disclosed
09/15/2026 VulDB entry created
09/15/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-61668 (🔒)
GCVE (CVE): GCVE-0-2026-61668
GCVE (VulDB): GCVE-100-404417
Entry
Created: 09/15/2026 19:57Changes: 09/15/2026 19:57 (65)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.