Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-rmjh-cf9q-pv7q

MEDIUMFix: directus/directus#25353

GHSA-rmjh-cf9q-pv7q is a medium-severity (CVSS 5.3) Information Exposure vulnerability in directus. O3 Security confirms whether GHSA-rmjh-cf9q-pv7q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Directus' exact version number is exposed by the OpenAPI Spec

Also known asCVE-2025-53887
Published
Jul 15, 2025
Updated
Jul 15, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

directusnpm
21Kdownloads / week

Description

Summary

The exact Directus version number is incorrectly being used as OpenAPI Spec version this means that it is being exposed by the /server/specs/oas endpoint without authentication.

Impact

With the exact version information a malicious attacker can look for known vulnerabilities in Directus core or any of its shipped dependencies in that specific running version.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmdirectusall versions11.9.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for directus. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update directus to 11.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rmjh-cf9q-pv7q is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-rmjh-cf9q-pv7q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rmjh-cf9q-pv7q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The exact Directus version number is incorrectly being used as OpenAPI Spec version this means that it is being exposed by the `/server/specs/oas` endpoint without authentication. ### Impact With the exact version information a malicious attacker can look for known vulnerabilities in Directus core or any of its shipped dependencies in that specific running version.
O3 Security · Impact-Aware SCA

Is GHSA-rmjh-cf9q-pv7q in your dependencies?

O3 detects GHSA-rmjh-cf9q-pv7q across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.