CVE-2026-61836: Directus: Authorization-dependent response served from unsegmented cache key
Summary When response caching is enabled (CACHEENABLED=true), the cache-key derivation in api/src/utils/get-cache-key.ts includes only version, path, query, and accountability.user (plus a conditional ip). Authorization context beyond user (share, role, roles, admin, app, policies) is not part of the key. For share tokens this is load-bearing.
Published Jul 20, 2026
Affected packages
directus
- Ecosystem
- npm
- Affected
- < 12.0.0
- Fixed in
- 12.0.0
- Check
npm ls directus
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
When response caching is enabled (CACHE_ENABLED=true), the cache-key derivation in api/src/utils/get-cache-key.ts includes only version, path, query, and accountability.user (plus a conditional ip). Authorization context beyond user (share, role, roles, admin, app, policies) is not part of the key.
For share tokens this is load-bearing. Directus's share-authentication flow (api/src/services/shares.ts:100-105) issues a JWT without an id claim, so api/src/utils/get-accountability-for-token.ts never assigns accountability.user, leaving it null (the default from create-default-accountability.ts). Every share token, and every anonymous request, therefore reduces to user: null in the cache-key input. Two different shares (or an anonymous request and a share token) requesting the same URL with the same query produce identical cache keys. The first request populates the bucket with a permission-filtered response; subsequent hits from unrelated shares or anonymous clients receive that payload without any permission re-evaluation.
This is the web-cache pattern "authorization-dependent response cached under an unsegmented key" (cache key collision / missing authorization context in cache key, CWE-524 and CWE-639). Two adjacent read populations collide:
- Share to share:
Share Apopulates the cache,Share BreadsShare A's scoped response. - Share to anonymous (and the reverse): any unauthenticated client hitting the same URL retrieves cached share-scoped data without presenting any token.
Affected
- Config required:
CACHE_ENABLED=true(any store: memory, redis, memcached) plus at least one activedirectus_sharesrow. This is not a default-on bug:CACHE_ENABLEDships asfalse. The cache is documented as a production performance setting, so operators who enable it are the ones affected.
Vulnerability class
- CWE-524: Use of Cache Containing Sensitive Information
- CWE-639: Authorization Bypass Through User-Controlled Key (the key here is the derived cache key, not the URL)
- OWASP API3:2023: Broken Object Property Level Authorization
Impact
- Cross-share confidentiality breach. Any share's filtered response can be served to a holder of a different share token, or to an anonymous request, that hits the same URL and query. Shares are advertised as a mechanism to distribute scoped, read-only access to specific items; this bug makes every cached share response readable by any other share-token holder who can reach the URL (the item-detail admin UI uses a predictable pattern).
- Anonymous request can read share data. Anonymous requests also compute
user=null. An anonymous client hitting/items/articles?fields=*after a share request has populated the cache receives the share's scoped payload with zero authentication. - Password-protected share, derivative effect. Password protection lives only at
shares.login(JWT issuance). Once any share has populated the cache for a URL, an anonymous or alternate-share request to that URL retrieves the cached payload without exchanging the share password. This is the same cache-key collision surfacing as a password-protection bypass symptom, not a distinct mechanism. - Persistence. The leak persists for the
CACHE_TTLwindow (commonly 5 to 30 minutes).CACHE_AUTO_PURGEclears on mutating writes to cached collections but does not purge per-user or per-share. WithCACHE_STORE=redis(common in production) the poisoned bucket survives server restarts. - No write impact. The bypass is read-only.
Scope of the leak depends on the share's permission surface. A share with no backing role (directus_shares.role = null, the default) collapses visibility to the primary key, so the cache leaks only PKs. A share backed by a role with broader field access (the intended production setup for distributing useful content) leaks the full content that role can see on the scoped item.
Credited to tr4ce-ju.
References
- https://github.com/directus/directus/security/advisories/GHSA-c6w9-5g5j-jh2p
- https://nvd.nist.gov/vuln/detail/CVE-2026-61836
- https://github.com/directus/directus/pull/27707
- https://github.com/directus/directus/commit/7ba4efb97525d3af33570537c76e44baea767f13
- https://github.com/directus/directus/releases/tag/v12.0.0
- https://github.com/advisories/GHSA-c6w9-5g5j-jh2p
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-129239
Directus: Share update allows reassigning user_created and role
medium6.5Nov 16, 2026CVE-2026-61835
Directus: SSRF Protection Bypass via 0.0.0.0 in File Import
high7.7Jul 20, 2026CVE-2026-35408
Directus: Missing Cross-Origin Opener Policy
high8.7Apr 4, 2026CVE-2026-35409
Directus: SSRF Protection Bypass via IPv4-Mapped IPv6 Addresses in File Import
high7.7Apr 4, 2026CVE-2026-35410
Directus: Open Redirect via Parser Bypass in OAuth2/SAML Authentication Flow
medium6.1Apr 4, 2026CVE-2026-35411
Directus: Open Redirect in Admin 2FA Setup Page
medium4.3Apr 4, 2026
