Advisory

GHSA-fm3h-p9wm-h74h

Also known as: CVE-2025-30353

Summary

Directus's webhook trigger flows can leak sensitive data

Details

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
  1. Add a condition that is likely to fail.
  2. Trigger the Flow with any input data that will fail the condition.
  3. 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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2025-03-26 20:08 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

directus

npm · All systems

Affected

  • introduced 9.12.0, fixed 11.5.0 (semver)

Fixed versions

11.5.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences