GHSA-mvv8-v4jj-g47j: Directus: Sensitive fields exposed in revision history
- Identifier
- GHSA-mvv8-v4jj-g47j
- Published
- Record updated
- Affected
- directus < 11.17.0
- Fixed in
- 11.17.0
- released March 24, 2026, 11 days before disclosure
Summary
Directus stores revision records in `directus_revisions` when items are created or updated, but its revision snapshot code does not consistently pass data through `prepareDelta`. As a result, sensitive fields such as `token`, `tfa_secret`, `external_identifier`, `auth_data`, `credentials`, and AI provider API keys can be stored in plaintext. The payload redaction list used by Flows also omits these fields for `directus_users` operations, so they are written unredacted into flow logs. Any user or service account with read access to `directus_revisions` or flow logs can retrieve these values, which could enable account takeover or unauthorized use of third-party API keys.
Mitigation
The source does not state a fix yet. Check the original advisory for updates.
Related items
- MediumWhen Shuffling Fails: Token Recovery from Obfuscated KV CachesSimilar attack · Arxiv (cs.CR + cs.CL + cs.LG)
- InfoGapLeak: When Privacy-Preserving LLM-based Web Agents Become a Privacy RiskSimilar attack · Arxiv (cs.CR + cs.CL + cs.LG)
- InfoReports of AI-related child sexual abuse material rise 8,400% in two years, data showsSimilar attack · The Guardian Technology
- MediumGHSA-8835-xmqj-354h: pgEdge Go LLM Library discloses provider API key fragments in error messagesSimilar attack · GitHub Advisory Database
- MediumPrivacy Leakage from Recurrent State in LLM InferenceSimilar attack · Arxiv (cs.CR + cs.CL + cs.LG)