GHSA-9cvc-v7wm-992c
MEDIUMGHSA-9cvc-v7wm-992c is a medium-severity (CVSS 5.3) CWE-862 vulnerability in @keystone-6/core. O3 Security confirms whether GHSA-9cvc-v7wm-992c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
When `ui.isAccessAllowed` is `undefined`, the `adminMeta` GraphQL query is publicly accessible
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@keystone-6/corenpmDescription
Summary
When ui.isAccessAllowed is undefined, the adminMeta GraphQL query is publicly accessible, that is to say, no session is required for the query.
This is different to the behaviour of the default AdminUI middleware, which by default will only be publicly accessible if a session strategy is not defined.
Impact
This vulnerability does not affect developers using the @keystone-6/auth package, or any users that have written their own ui.isAccessAllowed (that is to say, you are unaffected if ui.isAccessAllowed is defined).
This vulnerability does affect developers who thought that their session strategy will, by default, enforce that adminMeta is inaccessible by the public in accordance with that strategy; akin to the behaviour of the AdminUI middleware.
Patches
This vulnerability has been patched in @keystone-6/core version 5.5.1.
Workarounds
You can opt to write your own isAccessAllowed to work-around this vulnerability.
References
Pull request https://github.com/keystonejs/keystone/pull/8771
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @keystone-6/core | all versions | 5.5.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @keystone-6/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @keystone-6/core to 5.5.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9cvc-v7wm-992c is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-9cvc-v7wm-992c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-9cvc-v7wm-992c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-9cvc-v7wm-992c in your dependencies?
O3 detects GHSA-9cvc-v7wm-992c across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.