Servers and applications
GHSA-fq27-7m2r-q6vm
Manual trigger Flows can be executed by unauthenticated users
- Severity
- Medium 6.5
- Published
- 20 Aug 2026
- Last changed
- 20 Aug 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 12.2.0
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read some data · Change some data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N- Sources
- Project advisories (GitHub)
Description
Flows with a manual trigger are intended to be executable only by an authenticated user. The authentication check in the manual trigger handler only verified that an accountability object was present on the request. Unauthenticated API requests are assigned a default public accountability object, which satisfied that check, so anonymous callers were not rejected. Authorization then fell through to the permission check, which resolves an accountability object without a user or role to the Public role.
As a result, an unauthenticated request to the public trigger endpoint (POST /flows/trigger/:id) could execute an active manual Flow whenever the Flow is enabled for a collection that the Public role can read.
This is an incomplete fix of CVE-2025-53889 (GHSA-7cvf-pxgp-42fc). The guard introduced in 11.9.0 added a permission check on the target collection and items, but did not distinguish public accountability from an authenticated identity.
Workarounds
If upgrading is not immediately possible, any of the following reduce or remove exposure:
- Remove Public role read access from collections that are selected on manual Flows.
- Disable manual Flows that are attached to publicly readable collections, or convert them to a trigger type that is not publicly reachable.
- Review manual Flows for operations that run with full permissions and scope them down.
Affected software
| Software | Affected versions |
|---|---|
DirectusServers and applications · github:directus/directus |
|
About Directus
The flexible backend for all your projects 🐰 Turn your DB into a headless CMS, admin panels, or apps with a custom UI, instant APIs, auth & more.
- Weekly downloads (npm)
- 30,924npm, 15 Nov 2026
- Docker Hub pulls
- 50,954,770Docker Hub, 15 Nov 2026
- GitHub stars
- 38,722GitHub, 15 Nov 2026
- Forks
- 5,000GitHub, 15 Nov 2026
- Latest release
- v12.6.1GitHub, 15 Nov 2026
- Released
- 4 Nov 2026GitHub
- First published on GitHub
- 12 Dec 2012GitHub
Source code Website Docker image Package
Vulnerabilities in Directus
- In our list
- 85
- Published in the last 12 months
- 40
- Critical, last 12 months
- 3
- High, last 12 months
- 16
- Known exploited
- 0
- CVE-2026-126539Directus before 12.1.0 Authorization Bypass via Public WebSocket REST InterfaceCritical 9.2 11 Nov 2026
- GHSA-jvxj-w2qp-5vmxIP-restricted policies bypassed via GraphQL WebSocket subscriptionsMedium 6.8 30 Oct 2026
- GHSA-95f8-mvw7-gpj9File uploads can write into the extensions directory, leading to code execution in overlapping storage configurationsMedium 6.6 30 Oct 2026
- GHSA-32cw-mf7w-gpqrAuthenticated persistent Denial of Service via prototype pollution in CSV importHigh 7.1 30 Oct 2026
- GHSA-xf86-hfpm-92xrAI Chat route exposes admin-only tools to non-admin usersLow 3.1 19 Oct 2026
- GHSA-2xcm-7h22-3m66Update and delete by query evaluate filters without read permissions, leaking hidden field valuesMedium 6.5 19 Oct 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-fq27-7m2r-q6vm
- github.com https://github.com/directus/directus/security/advisories/GHSA-fq27-7m2r-q6vm