{"answers":{"affected":"4 open source packages ship an affected version, including @directus/api and directus. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-26185 in the wild and no public exploit code.","fix":"Upgrade @directus/api to 32.2.0 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-26185 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-26185 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @directus/api (npm): affected all versions; fixed in 32.2.0\n- @directus/api (npm): affected all versions; fixed in 32.2.0\n- directus (npm): affected all versions; fixed in 11.14.1\n- directus (npm): affected all versions; fixed in 11.14.1\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-26185/ (Markdown: https://insights.sbomify.com/CVE-2026-26185/index.md)","id":"CVE-2026-26185","markdown":"https://insights.sbomify.com/CVE-2026-26185/index.md","name":"CVE-2026-26185","record":{"aliases":["GHSA-jr94-gj3h-c8rf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Directus API dashboard","requires_auth":"none","summary":"Attackers can enumerate valid users via timing differences in password reset responses, exposing user existence information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"directus","vendor":"monospace"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Directus Affected by User Enumeration via Password Reset Timing Attack","id":"CVE-2026-26185","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":"monospace:directus","products":["monospace:directus"],"type":"information_disclosure","year":"2026"},"n_packages":4,"n_references":4,"next":{"headline":"Fleet has a SQL injection via backtick escape in ORDER BY parameter","id":"CVE-2026-26186"},"packages":[{"ecosystem":"npm","fixed":["32.2.0"],"introduced":["0"],"last_affected":[],"package":"@directus/api","purl":null,"source":"GHSA-jr94-gj3h-c8rf"},{"ecosystem":"npm","fixed":["32.2.0"],"introduced":["0"],"last_affected":[],"package":"@directus/api","purl":"pkg:npm/%40directus/api","source":"GHSA-jr94-gj3h-c8rf"},{"ecosystem":"npm","fixed":["11.14.1"],"introduced":["0"],"last_affected":[],"package":"directus","purl":null,"source":"GHSA-jr94-gj3h-c8rf"},{"ecosystem":"npm","fixed":["11.14.1"],"introduced":["0"],"last_affected":[],"package":"directus","purl":"pkg:npm/directus","source":"GHSA-jr94-gj3h-c8rf"}],"prev":{"headline":"Windows Projected File System Elevation of Privilege Vulnerability","id":"CVE-2026-26184"},"products":["@directus/api","directus"],"published":"2026-02-12","related":[{"cvss_score":9.8,"headline":"Insecure default value for CORS configuration","id":"CVE-2022-26969","kev_date_added":null,"published":"2022-12-26"},{"cvss_score":9.3,"headline":"Directus allows unauthenticated file upload and file modification due to lacking input sanitization","id":"CVE-2025-55746","kev_date_added":null,"published":"2025-08-20"},{"cvss_score":8.7,"headline":"Directus is Missing Cross-Origin Opener Policy","id":"CVE-2026-35408","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":8.6,"headline":"Directus: Authorization-dependent response served from unsegmented cache key","id":"CVE-2026-61836","kev_date_added":null,"published":"2026-07-15"},{"cvss_score":8.6,"headline":"Directus's webhook trigger flows can leak sensitive data","id":"CVE-2025-30353","kev_date_added":null,"published":"2025-03-26"},{"cvss_score":8.5,"headline":"Directus has a Path Traversal and Broken Access Control in File Management API","id":"CVE-2026-39942","kev_date_added":null,"published":"2026-04-09"},{"cvss_score":8.2,"headline":"Directus MySQL accent insensitive email matching","id":"CVE-2024-27295","kev_date_added":null,"published":"2024-03-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-13","vendors":["directus"]},"summary":"Attackers can enumerate valid users via timing differences in password reset responses, exposing user existence information.","url":"https://insights.sbomify.com/CVE-2026-26185/"}