Directus stores revision records (in directus_revisions) whenever items are created or updated. Due to the revision snapshot code not consistently calling the prepareDelta sanitization pipeline, sensitive fields (including user tokens, two-factor authentication secrets, external auth identifiers, auth data, stored credentials, and AI provider API keys) could be stored in plaintext within revision records.
Any user or service account with read access to directus_revisions (or flow logs) could retrieve values for fields that are supposed to be concealed or encrypted at rest, including:
- token, tfa_secret, external_identifier, auth_data, credentials
- ai_openai_api_key, ai_anthropic_api_key, ai_google_api_key, ai_openai_compatible_api_key
This could lead to account takeover (via stolen tokens or 2FA secrets) or unauthorized use of third-party API keys stored against users.
{
"github_reviewed": true,
"github_reviewed_at": "2026-04-04T06:12:07Z",
"cwe_ids": [
"CWE-200",
"CWE-312"
],
"severity": "MODERATE",
"nvd_published_at": "2026-04-09T17:16:29Z"
}