CVE-2025-30353

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.

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.

CVE-2025-30353 has a CVSS score of 8.6 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (11.5.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-30353? CVE-2025-30353 is a high-severity security vulnerability in directus (npm), affecting versions >= 9.12.0, < 11.5.0. It is fixed in 11.5.0.
2. How severe is CVE-2025-30353? CVE-2025-30353 has a CVSS score of 8.6 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of directus are affected by CVE-2025-30353? directus (npm) versions >= 9.12.0, < 11.5.0 is affected.
4. Is there a fix for CVE-2025-30353? Yes. CVE-2025-30353 is fixed in 11.5.0. Upgrade to this version or later.
5. Is CVE-2025-30353 exploitable, and should I be worried? Whether CVE-2025-30353 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-30353 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-30353? Upgrade directus to 11.5.0 or later.