High

Directus's webhook trigger flows can leak sensitive data

  • Disclosed: 26.03.2025
  • Updated: 11.10.2026 10:22

Describe the Bug

In Directus, when a Flow with the "Webhook" trigger and the "Data of Last Operation" response body encounters a ValidationError thrown by a failed condition operation, the API response includes sensitive data. This includes environmental variables, sensitive API keys, user accountability information, and operational data.

This issue poses a significant security risk, as any unintended exposure of this data could lead to potential misuse.

Image Image Image

To Reproduce

Steps to Reproduce:

  1. Create a Flow in Directus with:
    • Trigger: Webhook
    • Response Body: Data of Last Operation
  2. Add a condition that is likely to fail.
  3. Trigger the Flow with any input data that will fail the condition.
  4. Observe the API response, which includes sensitive information like:
    • Environmental variables ($env)
    • Authorization headers
    • User details under $accountability
    • Previous operational data.

Expected Behavior: In the event of a ValidationError, the API response should only contain relevant error messages and details, avoiding the exposure of sensitive data.

Actual Behavior: The API response includes sensitive information such as:

  • Environment keys (FLOWS_ENV_ALLOW_LIST)
  • User accountability (role, user, etc.)
  • Operational logs (current_payments, $last), which might contain private details.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package directus >= 9.12.0, < 11.5.0 11.5.0

References

CVSS score 8.6/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Weakness (CWE)
CWE-200
Platform
npm
Package
directus
Disclosed
26.03.2025
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-fm3h-p9wm-h74h - CC BY 4.0

Vulnerability history: directus

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (58) in the archive
Total entries
58
First → latest
04.2022 07.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 2
  • High 19
  • Medium 34
  • Low 3

Disclosures per year

  1. 2022: 4
  2. 2023: 8
  3. 2024: 14
  4. 2025: 17
  5. 2026: 15
Severity:
  1. High · 7.7 CVE-2026-61835 < 12.0.0 12.0.0
  2. High · 8.7 CVE-2026-35408 < 11.17.0 11.17.0
  3. Directus's webhook trigger flows can leak sensitive data this entry
    High · 8.6 CVE-2025-30353 >= 9.12.0, < 11.5.0 11.5.0
  4. High · 7.5 CVE-2024-54151 >= 11.0.0, < 11.3.0 11.3.0
  5. High · 7.4 CVE-2024-45596 < 10.13.3, >= 11.0.0-rc.1, < 11.1.0 10.13.3, 11.1.0
  6. High · 7.5 CVE-2024-39896 >= 9.11, < 10.13.0 10.13.0
  7. High · 6.3 CVE-2024-39701 >= 9.23.0, < 10.6.0 10.6.0
  8. High · 8.2 CVE-2024-27295 < 10.8.3 10.8.3
  9. High · 7.5 CVE-2023-45820 >= 10.4.0, < 10.6.2 10.6.2
  10. High · 7.6 ghsa-22rr-f3p8-5gf8 < 10.6.0 10.6.0
  11. Critical · 9.8 CVE-2022-26969 < 9.7.0 9.7.0
Show more (1) Showing 20 of 21

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.