CVE-2026-39943 Directus exposes sensitive fields in revision history

Medium 6.5 Published Updated

Attackers can read sensitive plaintext data like tokens and API keys from revision history due to missing sanitization in Directus.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-39943?

CVE-2026-39943 is a medium-severity vulnerability in Monospace Directus, published on 9 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official 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.

Weakness: CWE-312, CWE-200

Which versions are affected by CVE-2026-39943?

2 open source packages ship an affected version, including directus. It affects 1 product.

PackageAffectedFixed in
directus npmAll versions11.17.0
directus npmAll versions11.17.0

Products include Monospace Directus.

How do I fix CVE-2026-39943?

Upgrade directus to 11.17.0 or later.

Is CVE-2026-39943 being exploited?

There is no known exploitation of CVE-2026-39943 in the wild and no public exploit code.

All Monospace Directus vulnerabilities

Sources

Also known as GHSA-mvv8-v4jj-g47j.

Is CVE-2026-39943 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free