Project Subscriptions
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-mvv8-v4jj-g47j | Directus: Sensitive fields exposed in revision history |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 14 Apr 2026 17:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Monospace
Monospace directus |
|
| CPEs | cpe:2.3:a:monospace:directus:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Monospace
Monospace directus |
Fri, 10 Apr 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 10 Apr 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Directus
Directus directus |
|
| Vendors & Products |
Directus
Directus directus |
Thu, 09 Apr 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Directus is a real-time API and App dashboard for managing SQL database content. Prior to 11.17.0, 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. This vulnerability is fixed in 11.17.0. | |
| Title | Directus exposes sensitive fields in revision history | |
| Weaknesses | CWE-200 CWE-312 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-10T14:06:06.440Z
Reserved: 2026-04-07T22:40:33.820Z
Link: CVE-2026-39943
Updated: 2026-04-10T14:06:03.620Z
Status : Analyzed
Published: 2026-04-09T17:16:29.960
Modified: 2026-04-14T17:34:15.280
Link: CVE-2026-39943
No data.
OpenCVE Enrichment
Updated: 2026-04-15T16:00:07Z
Github GHSA