dbcve.org
DirectusApplication · Monospace

CVE-2026-39943

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-09
Fix available
A fix is available. Upgrade to 11.17.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Directus versions prior to 11.17.0 fail to sanitize sensitive fields through the prepareDelta pipeline when storing revision records in the directus_revisions table. This causes plaintext storage of credentials, API keys, 2FA secrets, and authentication tokens that should have been redacted, creating a data exposure vector.

MitigationUpgrade Directus to version 11.17.0 or later. Additionally, audit and purge existing revision records containing sensitive data, as the fix only prevents future leakage.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DirectusApplication
Affected:< 11.17.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Directus version
    Run `npm list directus` in the project directory, check package.json, or query the Directus API endpoint `/server/info`. Compare the version number to 11.17.0.
    Affected if The installed version is below 11.17.0
  2. Verify the directus_revisions table contains data
    Connect to the database and query the directus_revisions table with `SELECT COUNT(*) FROM directus_revisions;` or inspect its existence and row count.
    Affected if The table exists and contains revision records
  3. Inspect revision records for sensitive field names
    Query the revisions table for entries containing field names commonly associated with sensitive data, such as: `SELECT * FROM directus_revisions WHERE JSON_KEYS(data) LIKE '%password%' OR JSON_KEYS(data) LIKE '%token%' OR JSON_KEYS(data) LIKE '%secret%' OR JSON_KEYS(data) LIKE '%key%';`
    Affected if Revision records contain keys referencing passwords, tokens, secrets, or API keys
  4. Check for plaintext sensitive values in revision data
    Examine the actual data payload in the directus_revisions table for plaintext credentials, API keys, 2FA secrets, or authentication tokens stored in fields that should have been redacted.
    Affected if Plaintext sensitive values are present in the revision records

You are affected if running Directus version below 11.17.0 and the directus_revisions table contains plaintext sensitive data that should have been redacted.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.17.0 or later
Fixed in 11.17.0
Interim mitigation

Upgrade Directus to version 11.17.0 or later. Additionally, audit and purge existing revision records containing sensitive data, as the fix only prevents future leakage.

Recommended fix High confidence

Directus 11.17.0

  1. Upgrade Directus to version 11.17.0 or later to resolve the vulnerability
  2. After upgrading, review existing revision records in the directus_revisions table to confirm no sensitive data remains from prior versions
  3. Consult the Directus 11.17.0 release notes for any required migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Directus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39943 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39943 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data