Skip to main content
VulnerabilityPublished

CVE-2025-64749: directus · Observable Discrepancy

Affects directusSource GCVE Database

0
Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 11.13.0 when convenient.

Data as of 14 Nov 2026, 20:43 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.14.3
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 11.13.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.

What to do

Upgrade directus to 11.13.0.

Affected software

ProductAffectedFixed in
directus directusAffected
  • <11.13.0
Fixed in
  • 11.13.0

AI-suggested

Upgrade Directus to version 11.13.0 or later, where this issue is fixed. No additional mitigation is required as the vendor has provided an official fix.

Description

Directus versions prior to 11.13.0 have an information disclosure vulnerability where the REST API returns different error messages for unauthorized access to existing collections versus access to non-existing collections. This discrepancy leaks the existence of collections to unauthorized users. The issue is fixed in version 11.13.0.

References

Community reviews

Loading reviews…