ZDF
Sign inSign up

Vulnerabilities

Security fix · GHSA-jvxj-w2qp-5vmx

IP-restricted policies bypassed via GraphQL WebSocket subscriptions

Published Oct 30, 2026 · catalog updated Oct 30, 2026 · IP-restricted policies bypassed via

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-jvxj-w2qp-5vmx. A missing EPSS score is not a low risk. Compare IP-restricted policies bypassed via 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 (IP-restricted policies bypassed via).
  • 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.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
npm directus

## Summary Directus did not forward the client's IP address, user agent or origin when accepting GraphQL WebSocket (subscription) connections. Policies that restrict access by IP ( ) treat a missing IP as "no restriction" when resolving admin and app access. A user with a policy granting only from a trusted network could therefore connect over the GraphQL WebSocket endpoint from any network and receive full admin access. In addition, the global access cache key ignored the client IP. An elevated result from the WebSocket path could be cached and returned for the same user's subsequent REST and GraphQL HTTP requests, extending the bypass beyond the WebSocket connection until the cache entry expired. ## Impact Deployments are affected if they use GraphQL WebSockets (enabled by default when WebSockets are enabled) and rely on to limit when a policy's or applies. An authenticated user holding such a policy can bypass the network restriction and act as an administrator from outside the allowed range. Activity records for actions taken over the GraphQL WebSocket path were also written without IP, user agent or origin. Deployments that do not use on policies are not affected by the access bypass. ## Patches Fixed in 12.4.0. The GraphQL WebSocket handshake now carries the request's IP, user agent and origin into the connection's accountability (#27813, released in 12.1.0), and the global access cache is now keyed on the client IP (#28190, released in 12.4.0). ## Workarounds Disable GraphQL WebSockets with , or avoid granting through policies whose only safeguard is . ## Credits Reported by [pavelkohout396](https://github.com/pavelkohout396)

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.0.0, < 12.4.0

How to fix GHSA-jvxj-w2qp-5vmx

  • Upgrade

    GHSA-jvxj-w2qp-5vmx lists a fix boundary at 12.4.0. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 12.4.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-jvxj-w2qp-5vmx. A missing EPSS score is not a low risk. Compare IP-restricted policies bypassed via with the linked advisory before you change production.

Which versions are affected?

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

What should an analyst verify?

CWE-284: Improper Access Control; CWE-778; CWE-863: Incorrect Authorization. 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. Oct 30, 2026 · Maintainer security tabs

    Detected

    ## Summary Directus did not forward the client's IP address, user agent or origin when accepting GraphQL WebSocket (subscription) connections. Policies that restrict access by IP ( ) treat a missing IP as "no restriction" when resolving admin and app access. A user with a policy granting only from a trusted network could therefore connect over the GraphQL WebSocket endpoint from any network and re

Sources

  • Maintainer security tabsVendor advisoryGHSA-jvxj-w2qp-5vmx

    ## Summary Directus did not forward the client's IP address, user agent or origin when accepting GraphQL WebSocket (subscription) connections. Policies that restrict access by IP ( ) treat a missing IP as "no restriction" when resolving admin and app access. A user with a policy granting only from a trusted network could therefore connect over the GraphQL WebSocket endpoint from any network and re

    github.com

Freshness

Last verified in this catalog Oct 30, 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