{"items":[{"id":"NVI-00015372","kind":"vulnerability","title":"Directus Allows Single Sign-On User Enumeration","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jgf4-vwc3-r46v","CVE-2024-39896"],"plain_summary":"GitHub lists this reviewed advisory for directus. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-1696c84bb1ae97430396cdeadfdb4670"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-16T15:40:35.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-61c96c699817d288027dbfe5b078ba88"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"0.506%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.43242. Missing scores are unknown.","source_id":"sr-1696c84bb1ae97430396cdeadfdb4670"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-61c96c699817d288027dbfe5b078ba88","url":"https://github.com/advisories/GHSA-jgf4-vwc3-r46v","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jgf4-vwc3-r46v","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T19:09:30.244Z"},{"id":"sr-1696c84bb1ae97430396cdeadfdb4670","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2024-39896","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:44:07.762Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-61c96c699817d288027dbfe5b078ba88"],"technology":"directus","known_exclusions":[],"conditions_summary":"### Impact\nWhen relying on SSO providers in combination with local authentication it can be possible to enumerate existing SSO users in the instance. This is possible because if an email address exists in Directus and belongs to a known SSO provider then it will throw a \"helpful\" error that the user belongs to another provider.\n\n### Reproduction\n\n1. Create a user using a SSO provider `test@directus.io`.\n2. Try to log-in using the regular login form (or the API)\n3. When using a valid email address\n\n| **APP** | **API** |\n| --- | --- |\n| !image | !image |\n\n4. When using an invalid email address\n\n| **APP** | **API** |\n| --- | --- |\n| !image | !image |\n\n5. Using this differing error it is possible to determine whether a specific email address is present in the Directus instance as an SSO user.\n\n### Workarounds\nWhen only using","public_affected_ranges":[">= 9.11, < 10.13.0"]}],"null_published_at":"2026-11-06T00:29:57.325Z","source_updated_at":"2026-09-16T15:40:35.000Z","source_disclosed_at":"2024-07-08T18:41:57.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-01T19:09:30.244Z"},{"id":"NVI-00015372","kind":"vulnerability","title":"Directus Allows Single Sign-On User Enumeration","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jgf4-vwc3-r46v","CVE-2024-39896"],"plain_summary":"GitHub lists this reviewed advisory for directus. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-61c96c699817d288027dbfe5b078ba88"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-09-16T15:40:35.000Z","value":"7.5 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-61c96c699817d288027dbfe5b078ba88"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-61c96c699817d288027dbfe5b078ba88","url":"https://github.com/advisories/GHSA-jgf4-vwc3-r46v","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jgf4-vwc3-r46v","publisher":"GitHub Advisory Database","observed_at":"2026-11-01T19:09:30.244Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-61c96c699817d288027dbfe5b078ba88"],"technology":"directus","known_exclusions":[],"conditions_summary":"### Impact\nWhen relying on SSO providers in combination with local authentication it can be possible to enumerate existing SSO users in the instance. This is possible because if an email address exists in Directus and belongs to a known SSO provider then it will throw a \"helpful\" error that the user belongs to another provider.\n\n### Reproduction\n\n1. Create a user using a SSO provider `test@directus.io`.\n2. Try to log-in using the regular login form (or the API)\n3. When using a valid email address\n\n| **APP** | **API** |\n| --- | --- |\n| !image | !image |\n\n4. When using an invalid email address\n\n| **APP** | **API** |\n| --- | --- |\n| !image | !image |\n\n5. Using this differing error it is possible to determine whether a specific email address is present in the Directus instance as an SSO user.\n\n### Workarounds\nWhen only using","public_affected_ranges":[">= 9.11, < 10.13.0"]}],"null_published_at":"2026-11-03T10:03:31.358Z","source_updated_at":"2026-09-16T15:40:35.000Z","source_disclosed_at":"2024-07-08T18:41:57.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-01T19:09:30.244Z"}],"next_cursor":null,"snapshot_revision":"42594"}