DIRAC: SQL injection and lack of access control in PilotManager service

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Details A number of the functions in PilotManager pass parameters directly through to the database layer, which then does not do any escaping on the parameters. For example setPilotStatus: https://github.com/DIRACGrid/DIRAC/blob/1738e7c6d2f31d26f1364255d9d2e87b4896c922/src/DIRAC/WorkloadManagementSystem/Service/PilotManagerHandler.py#L343-L349 https://github.com/DIRACGrid/DIRAC/blob/1738e7c6d2f31d26f1364255d9d2e87b4896c922/src/DIRAC/WorkloadManagementSystem/DB/PilotAgentsDB.py#L117 This won't accept multiple statements separated by a semicolon, but a carefully crafted set of parameters containing SQL escapes would likely be able to change or return other database entries. Further to this, the PilotManager access control is only set to "authenticated"; this allows these functions to be called by any user. This allows any user to manage (e.g. delete, read output of) any pilot pilot job:…

Published by the source

13 Jul 2026, 18:38 UTC

Last modified by the source

13 Jul 2026, 18:46 UTC

Source last checked

26 Oct 2026, 13:46 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-7xw9-549r-8jrc

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-7xw9-549r-8jrc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-7xw9-549r-8jrc

Advisory: DIRAC: SQL injection and lack of access control in PilotManager service
IDs: GHSA-7xw9-549r-8jrc
Record: https://patchnext.com/advisories/ghsa-7xw9-549r-8jrc (revision 2, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: dirac 9.1.10, 9.0.22, 8.0.79. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI dirac: affected >= 6, < 8.0.79; >= 8.1.0a1, < 9.0.22; >= 9.1.0, < 9.1.10; fixed in 9.1.10, 8.0.79, 9.0.22

## Suggested inspection (read-only)
- `python -m pip show dirac`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dirac.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-7xw9-549r-8jrc (OSV record GHSA-7xw9-549r-8jrc lists affected ranges: PyPI dirac >=6 =8.1.0a1 =9.1.0 <9.1.10 (fixed))
- Verified: https://github.com/advisories/GHSA-7xw9-549r-8jrc (GitHub-reviewed advisory GHSA-7xw9-549r-8jrc lists affected ranges: PyPI dirac >=6 =8.1.0a1 =9.1.0 <9.1.10)

Commands are suggestions: review each one before running it.