Which versions of Directus are affected by CVE-2026-10716?

A SQL injection vulnerability in Directus before v12.1.0 could allow compromised administrator accounts to directly access and manipulate production data in PostgreSQL databases.. A patch is available.

How to fix or mitigate CVE-2026-10716?

Within 24 hours, inventory all Directus deployments and their versions, and immediately audit administrator credentials for unauthorized access or compromise indicators. Within 7 days, upgrade all instances to Directus v12.1.0 or later. Within 30 days, implement stricter administrator access controls, review authentication logs for anomalous activity during collection creation, and restrict PostGIS extension privileges to only required administrator accounts.

Directus CVE-2026-10716

Q: What is the CVSS score of CVE-2026-10716?

CVE-2026-10716 has a CVSS 4.0 base score of 7.5 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

EUVD-2026-53519 HIGH

SQL Injection (CWE-89)

2026-08-05 Fluid Attacks

GHSA-c4h6-c3hj-2qc3

SQLi PostgreSQL Directus

7.5

CVSS 4.0 · Vendor: Fluid Attacks

Severity by source

Vendor (Fluid Attacks) PRIMARY

7.5 HIGH

CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

6.6 MEDIUM

PostGIS must be installed and enabled on PostgreSQL (condition beyond attacker control → AC:H); Directus administrator credentials required → PR:H; full database confidentiality, integrity, and availability impact within unchanged scope.

3.1 AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Fluid Attacks).

CVSS VectorVendor: Fluid Attacks

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Aug 05, 2026 - 17:51 vuln.today

CVE Published

Aug 05, 2026 - 16:50 cve.org

HIGH 7.5

DescriptionCVE.org

Directus contains an authenticated SQL injection vulnerability in the collection creation flow when the instance uses PostgreSQL with PostGIS enabled. An administrator can create a collection with a geometry field whose fields[].type value starts with geometry but contains attacker-controlled SQL syntax after the geometry subtype.This issue affects Directus: before 12.1.0.

AnalysisAI

SQL injection in Directus before 12.1.0 enables an authenticated administrator to execute arbitrary SQL against the underlying PostgreSQL database during collection creation by embedding attacker-controlled SQL syntax within a geometry field type value. The attack is gated behind two non-default prerequisites - administrator-level credentials and a PostgreSQL backend with the PostGIS extension installed - which together constrain the realistic threat surface to insider risk or compromised admin accounts. A vendor patch is confirmed available in v12.1.0; no public exploit code or CISA KEV listing has been identified at time of analysis.

Technical ContextAI

Directus is an open-source headless CMS and data platform (cpe:2.3:a:directus:directus:*:*:*:*:*:*:*:*) that abstracts SQL databases behind a REST/GraphQL API. When the database backend is PostgreSQL with the PostGIS geospatial extension enabled, Directus supports geometry field types during collection schema creation. The vulnerability (CWE-89 - Improper Neutralization of Special Elements used in an SQL Command) arises because the collection creation flow parses the fields[].type value and, when the value begins with the string 'geometry', uses the remainder of that string to construct a PostGIS column definition without adequate sanitization or parameterization. This allows an attacker to append raw SQL beyond the expected geometry subtype, which is then interpolated directly into a DDL or DML statement executed against PostgreSQL.

RemediationAI

The primary remediation is upgrading Directus to version 12.1.0 or later, which resolves the injection by properly sanitizing geometry field type input during collection creation. The patched release is available at https://github.com/directus/directus/releases#release-v12.1.0, and the full security advisory is published at https://github.com/directus/directus/security/advisories/GHSA-chfm-g7r3-vv42. If an immediate upgrade is not feasible, operators should consider the following compensating controls: first, disable the PostGIS extension on the PostgreSQL instance if geospatial features are not actively required - this eliminates the vulnerable code path entirely but loses all geospatial column type support. Second, strictly limit Directus administrator-level access to the minimum number of trusted accounts and enforce MFA on those accounts, since the vulnerability is only reachable with admin credentials. Third, audit collection creation API activity in Directus logs for anomalous geometry type strings containing SQL metacharacters as a detection measure.