dbcve.org
DirectusApplication · Monospace

CVE-2026-35409

HIGH · 7.7 CVSS v3.1 Published 2026-04-06
Fix available
A fix is available. Upgrade to 11.16.0 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Directus is a real-time API and App dashboard for managing SQL database content. Prior to 11.16.0, a Server-Side Request Forgery (SSRF) protection bypass has been identified and fixed in Directus. The IP address validation mechanism used to block requests to local and private networks could be circumvented using IPv4-Mapped IPv6 address notation. This vulnerability is fixed in 11.16.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 confidence

Directus prior to 11.16.0 has an SSRF protection bypass in its IP address validation mechanism. The protection designed to block requests to local/private networks can be circumvented by representing IPv4 addresses (like 127.0.0.1) in IPv4-Mapped IPv6 notation (::ffff:127.0.0.1), allowing attackers to access internal services.

MitigationUpgrade to Directus 11.16.0 or later, which includes proper validation to block IPv4-Mapped IPv6 addresses that map to private/local IPv4 addresses.

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
DirectusApplication
Affected:< 11.16.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Directus version
    Check the installed version via the admin dashboard (Settings > About), the API endpoint /server/info, or the package.json file in the installation directory
    Affected if The installed version is any version prior to 11.16.0 (e.g., 11.15.x, 11.14.x, earlier releases)
  2. Locate external request feature
    Identify if Directus has the Remote Sources or Request URL functionality enabled. Check the database table directus_settings for fields related to remote_sources, or inspect the admin panel for any configured external data sources or URL-based integrations
    Affected if External request capabilities (such as remote sources fetching data from URLs) are configured and active in the Directus instance
  3. Verify IP validation behavior
    Test the IP validation by attempting to trigger an outbound request to an internal IP address using standard IPv4 notation (e.g., http://192.168.1.1) versus IPv4-mapped IPv6 notation (e.g., http://[::ffff:192.168.1.1]). If direct API access is available, inspect how the /files or /remote-src endpoints handle URL validation
    Affected if The system accepts IPv4-mapped IPv6 addresses (::ffff:x.x.x.x format) as valid targets while blocking plain IPv4 private addresses, indicating the bypass is possible

You are affected if your Directus installation is version 11.15.x or earlier AND the remote source or URL fetching functionality is enabled, allowing attackers to bypass SSRF protections via IPv4-mapped IPv6 address notation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 11.16.0 or later
Fixed in 11.16.0
Interim mitigation

Upgrade to Directus 11.16.0 or later, which includes proper validation to block IPv4-Mapped IPv6 addresses that map to private/local IPv4 addresses.

Recommended fix High confidence

Directus 11.16.0

  1. 1. Backup your Directus installation and database before proceeding with the upgrade.
  2. 2. Check your current Directus version to confirm it is below 11.16.0.
  3. 3. Consult the official Directus upgrade documentation for your deployment method (Docker, npm, etc.).
  4. 4. Upgrade Directus to version 11.16.0 or later.
  5. 5. Verify the upgrade was successful by checking the Directus version in the admin panel or via API.
  6. 6. Test that SSRF protection is working correctly - ensure requests to local/private network addresses are properly blocked, including IPv4-Mapped IPv6 addresses.
Caveat Review the Directus 11.16.0 release notes for any breaking changes between your current version and 11.16.0

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Directus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35409 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35409 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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