# CVE-2026-26185: Directus Affected by User Enumeration via Password Reset Timing Attack

> Attackers can enumerate valid users via timing differences in password reset responses, exposing user existence information.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Feb 2026
- **Updated:** 13 Feb 2026
- **Also known as:** GHSA-jr94-gj3h-c8rf

## What is CVE-2026-26185?

CVE-2026-26185 is a medium-severity vulnerability in Monospace Directus, published on 12 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directus is a real-time API and App dashboard for managing SQL database content. Before 11.14.1, a timing-based user enumeration vulnerability exists in the password reset functionality. When an invalid reset_url parameter is provided, the response time differs by approximately 500ms between existing and non-existing users, enabling reliable user enumeration. This vulnerability is fixed in 11.14.1.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2026-26185?

4 open source packages ship an affected version, including @directus/api and directus. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@directus/api` | npm | All versions | 32.2.0 |
| `@directus/api` | npm | All versions | 32.2.0 |
| `directus` | npm | All versions | 11.14.1 |
| `directus` | npm | All versions | 11.14.1 |

Products: Monospace Directus.

## How do I fix CVE-2026-26185?

Upgrade @directus/api to 32.2.0 or later.

## Is CVE-2026-26185 being exploited?

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

## Other vulnerabilities in Monospace Directus

- [CVE-2022-26969](https://insights.sbomify.com/CVE-2022-26969/): Insecure default value for CORS configuration (critical 9.8)
- [CVE-2025-55746](https://insights.sbomify.com/CVE-2025-55746/): Directus allows unauthenticated file upload and file modification due to lacking input sanitization (critical 9.3)
- [CVE-2026-35408](https://insights.sbomify.com/CVE-2026-35408/): Directus is Missing Cross-Origin Opener Policy (high 8.7)
- [CVE-2026-61836](https://insights.sbomify.com/CVE-2026-61836/): Directus: Authorization-dependent response served from unsegmented cache key (high 8.6)
- [CVE-2025-30353](https://insights.sbomify.com/CVE-2025-30353/): Directus's webhook trigger flows can leak sensitive data (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26185 and fix it if it is affected.

What it is: CVE-2026-26185 is a medium-severity vulnerability in Monospace Directus, published on 12 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26185 in the wild and no public exploit code.

Affected packages and fixed versions:
- @directus/api (npm): affected all versions; fixed in 32.2.0
- @directus/api (npm): affected all versions; fixed in 32.2.0
- directus (npm): affected all versions; fixed in 11.14.1
- directus (npm): affected all versions; fixed in 11.14.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-26185/ (Markdown: https://insights.sbomify.com/CVE-2026-26185/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-26185
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-26185
- OSV: https://osv.dev/vulnerability/CVE-2026-26185

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-26185/
Summaries are generated and may contain mistakes; the official description above is the record.