DIRAC · CVE-2026-61668 · Package
FIX → 9.1.10 · 8.0.79 +1
DIRAC's pilot wrapper downloads its second-stage pilot script over HTTPS with certificate validation turned off, and the checksum file comes over the same unverified channel. A network attacker who can redirect that connection can swap in a script that runs with the pilot's proxy and credentials.
first public Jul 13, 2026 · 2 sources
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Grid sites and teams that run DIRAC pilots fetch the second-stage pilot from a web server during job setup. Exposure depends on whether an attacker can intercept or redirect that network path, such as through DNS or routing changes at a grid site. Teams that do not run DIRAC pilots can skip it.
Not affected if isolated-network, no-dirac-pilots
Who cares dirac, grid-computing, pilot-jobs, python
pip show DIRACUpgrade to 9.1.10 · 8.0.79 +1
The second stage pilot (pilot.tar) is downloaded by the initial wrapper script without any verification of the webservers' SSL certificate and the contained script is subsequently executed. The checksum is tested, but the reference checksum file is downloaded over the same unvalidated channel.
The pilot wrapper downloads and executes the main second stage pilot script, but the SSL validation on this connection is explicitly disabled (to match old python < 2.7.9 behaviour): https://github.com/DIRACGrid/DIRAC/blob/integration/src/DIRAC/WorkloadManagementSystem/Utilities/PilotWrapper.py#L292-L296
This means that the second stage pilot code is not verified in any way and could potentially be altered by a man-in-the-middle attack to execute arbitrary code in the pilot context (i.e. with access to the pilot proxy/credentials).
The HTTPS connection should be validated against both the system certificates and $X509_CERT_DIR and fail if neither validate correctly.
This would require a man-in-the-middle style attack against a grid site's network (i.e. changing the DNS or routing to redirect the pilot's connection); this is likely to be difficult which probably limits the potential impact.
https://pypi.org/project/DIRAC/8.0.79/ https://pypi.org/project/DIRAC/9.0.22/ https://pypi.org/project/DIRAC/9.1.10/
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
8.0.79 for the 8.0 line (affected >= 6.20.1, < 8.0.79)9.0.22 for the 9.0 line (affected >= 8.1.0a1, < 9.0.22)9.1.10 for the 9.1 line (affected >= 9.1.0, < 9.1.10)This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.