Quick answers
- Is CVE-2025-53887 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-53887 being exploited in the wild.
- How severe is CVE-2025-53887?
- Low severity, with a CVSS score of 3.1, published 15 July 2025.
- Which products and versions are affected?
- directus (npm) SEMVER:introduced=0,fixed=11.9.0.
- Is there a fix for CVE-2025-53887?
- Yes. directus (npm): upgrade to 11.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-53887 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-53887?
- Check whether you run 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 (npm): upgrade to 11.9.0 or later
npm install directus@11.9.0
Technical details
The Directus application incorrectly uses its exact version number as the OpenAPI specification version string, which is then exposed via the unauthenticated `/server/specs/oas` endpoint. This is an information disclosure vulnerability (CWE-200) where sensitive version metadata is accessible without authentication over the network. An attacker can query this endpoint to determine the exact Directus version running on a target system, then cross-reference known vulnerabilities in that version or its shipped dependencies to identify potential attack vectors. The vulnerability affects all versions from 9.0.0 through 11.8.x and is fixed in version 11.9.0.
Affected products
- Directus Directus 9.0.0 to 11.8.x
Identifiers
- CVE-2025-53887
- GHSA-rmjh-cf9q-pv7q
Timeline
- 2025-07-15: disclosed
- 2025-07-15: patched: Fixed in version 11.9.0