Is CVE-2026-26185 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-26185 being exploited in the wild.

How severe is CVE-2026-26185?

Low severity, with a CVSS score of 3.1, published 12 February 2026.

Which products and versions are affected?

@directus/api (npm) SEMVER:introduced=0,fixed=32.2.0; directus (npm) SEMVER:introduced=0,fixed=11.14.1.

Is there a fix for CVE-2026-26185?

Yes. @directus/api (npm): upgrade to 32.2.0 or later; directus (npm): upgrade to 11.14.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-26185 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-26185?

Check whether you run @directus/api (npm) or directus (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-26185: Directus user enumeration via password reset timing attack

CVE-2026-26185 · Severity: low · CVSS 3.1 · Published 2026-02-12

Directus is a popular open-source headless CMS and API platform. A timing-based vulnerability in its password reset functionality allows attackers to enumerate valid user accounts by measuring response delays, potentially enabling targeted phishing campaigns and account enumeration attacks.

Technologies: @directus/api (npm), directus (npm). Vendors: npm.

Quick answers

Is CVE-2026-26185 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-26185 being exploited in the wild.
How severe is CVE-2026-26185?: Low severity, with a CVSS score of 3.1, published 12 February 2026.
Which products and versions are affected?: @directus/api (npm) SEMVER:introduced=0,fixed=32.2.0; directus (npm) SEMVER:introduced=0,fixed=11.14.1.
Is there a fix for CVE-2026-26185?: Yes. @directus/api (npm): upgrade to 32.2.0 or later; directus (npm): upgrade to 11.14.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-26185 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-26185?: Check whether you run @directus/api (npm) or directus (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@directus/api (npm): upgrade to 32.2.0 or later
```
npm install @directus/api@32.2.0
```
directus (npm): upgrade to 11.14.1 or later
```
npm install directus@11.14.1
```

Technical details

The vulnerability is a timing-based user enumeration (CWE-203) in the password reset endpoint. The password reset mechanism includes timing protection to prevent enumeration; however, URL parameter validation executes before this protection is applied. When an attacker provides an invalid reset_url parameter, the response time differs by approximately 500ms between existing and non-existing users, reliably revealing account existence. No authentication is required; exploitation requires only network access to the password reset endpoint. The vulnerability affects Directus versions up to 11.15.0 and @directus/api versions prior to 32.2.0, with fixes available in 11.15.0 and 32.2.0 respectively.

Affected products

Directus Directus ≤ 11.15.0
Directus @directus/api < 32.2.0

Identifiers

CVE-2026-26185
GHSA-jr94-gj3h-c8rf

Timeline

2026-02-12: disclosed: Advisory GHSA-jr94-gj3h-c8rf published
2026-02-12: patched: Fixes available in Directus 11.15.0 and @directus/api 32.2.0

References

https://github.com/directus/directus/security/advisories/GHSA-jr94-gj3h-c8rf

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.