ZDF
Sign inSign up

Vulnerabilities

Security fix · GHSA-r9xq-xp38-j4j3

Sensitive fields, including plaintext AI backend authorization headers, readable by minimal users

Published Aug 20, 2026 · catalog updated Aug 20, 2026 · Sensitive fields, including plaintext

Last checked Nov 1, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-r9xq-xp38-j4j3. A missing EPSS score is not a low risk. Compare Sensitive fields, including plaintext with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Sensitive fields, including plaintext).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Medium6.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
npm directus

## Summary The built-in minimal app permissions granted unrestricted access to the singleton. As a result, any authenticated user with and no custom permissions could read every settings field, including server-side AI and MCP configuration that is intended to be admin-only. The highest impact field is , which stores the custom request headers used to authenticate against a self-configured OpenAI-compatible backend. Unlike the provider API key fields, this field is not encrypted or concealed, so any bearer token or API key an administrator placed there was returned in plaintext. ## Impact A user whose only privilege is app access could read, among others: - : plaintext authorization headers for the configured OpenAI-compatible backend - : internal or private endpoint of that backend - : server-side AI system prompt - : server-side MCP system prompt The data was reachable through both the REST ( ) and GraphQL ( ) system endpoints, since both resolve through the same permission layer. Where contained credentials, the disclosure is a usable secret rather than inert configuration: the value was confirmed to authenticate successfully against a backend that required it. This can lead to unauthorized use of, and billing against, the customer's AI provider account, and it discloses the internal endpoint that backend is hosted on. The encrypted provider key fields ( , ) were correctly masked and are not disclosed. Impact is reduced to disclosure of AI and MCP prompt text plus backend metadata on instances where is unset or holds no credential material. Prompt disclosure itself may still reveal operational or tenant-specific detail. Exploitation requires a valid, non-admin account on the instance. No user interaction, no custom permission, and no additional privilege is needed. ### Note for existing installations The patch changes the built-in minimal app permissions. In versions before 12.3.0, the policy creation dialog in the Data Studio also wrote app access permission row

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm directus>= 11.15.0, < 12.2.0

How to fix GHSA-r9xq-xp38-j4j3

  • Upgrade

    GHSA-r9xq-xp38-j4j3 lists a fix boundary at 12.2.0. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 12.2.0

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-r9xq-xp38-j4j3. A missing EPSS score is not a low risk. Compare Sensitive fields, including plaintext with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with >= 11.15.0, < 12.2.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-1220; CWE-200: Exposure of Sensitive Information; CWE-522: Insufficiently Protected Credentials. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Directus security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 20, 2026 · Maintainer security tabs

    Detected

    ## Summary The built-in minimal app permissions granted unrestricted access to the singleton. As a result, any authenticated user with and no custom permissions could read every settings field, including server-side AI and MCP configuration that is intended to be admin-only. The highest impact field is , which stores the custom request headers used to authenticate against a self-configured OpenAI-

Sources

  • Maintainer security tabsVendor advisoryGHSA-r9xq-xp38-j4j3

    ## Summary The built-in minimal app permissions granted unrestricted access to the singleton. As a result, any authenticated user with and no custom permissions could read every settings field, including server-side AI and MCP configuration that is intended to be admin-only. The highest impact field is , which stores the custom request headers used to authenticate against a self-configured OpenAI-

    github.com

Freshness

Last verified in this catalog Aug 20, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 1, 2026