CVE-2026-61835
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDirectus is a real-time API and App dashboard for managing SQL database content. Prior to 12.0.0, the SSRF protection on Directus's file-import-from-URL feature can be bypassed using the address 0.0.0.0 because api/src/request/is-denied-ip.ts treats 0.0.0.0 as a keyword for local interfaces but never blocks the literal address itself. On Linux and macOS, connecting to 0.0.0.0 reaches localhost, so an authenticated user with file-upload rights can make the server fetch internal services through the /files/import endpoint and retrieve the response as a downloadable file. This issue is fixed in version 12.0.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDirectus versions before 12.0.0 have a SSRF protection bypass in the file-import-from-URL feature. The IP validation in api/src/request/is-denied-ip.ts treats 0.0.0.0 as a keyword for local interfaces but fails to block the literal address 0.0.0.0 itself. Since Linux and macOS resolve 0.0.0.0 to localhost, an authenticated user with file-upload permissions can use the /files/import endpoint to make the server fetch internal services and retrieve responses as downloadable files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 12.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Directus versionCheck the installed Directus version by inspecting package.json, the /api/version endpoint, or the database directus_versions table. Compare against the affected range.Affected if The installed version is before 12.0.0 (e.g., 11.x.x or earlier)
-
Verify file-import-from-URL feature existsConfirm the Directus instance includes the file import from URL functionality by checking if the /files/import endpoint is present in the API routes or by reviewing the codebase for the import feature.Affected if The /files/import endpoint exists and is accessible in the Directus instance
-
Confirm file-upload permission configurationReview user roles and permissions in Directus admin panel under Settings > Roles & Permissions. Check if any role has create permission on the files collection.Affected if Any authenticated user role grants file-upload or files.create permissions
A Directus instance is affected if it runs a version before 12.0.0 and exposes the file-import-from-URL feature to users with file-upload permissions, allowing them to trigger server connections to 0.0.0.0.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped12.0.0
Upgrade Directus to version 12.0.0 or later to patch the SSRF bypass in the file-import URL feature.
Directus 12.0.0 or later
- 1. Back up your Directus instance database and configuration files before upgrading.
- 2. Upgrade Directus to version 12.0.0 or later.
- 3. Verify the upgrade was successful by checking the Directus version in the admin panel or via API.
- 4. Test the file-import-from-URL feature to confirm SSRF protection is working correctly.
- 5. Ensure only trusted users have file-upload permissions to reduce attack surface.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-61835 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-61835 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data