Quick answers
- Is CVE-2026-63396 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63396 being exploited in the wild.
- How severe is CVE-2026-63396?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- ROOST Coop before 1.0.0.
- Is there a fix for CVE-2026-63396?
- Yes: fixed in 1.0.0. Until then: Running the service on an authenticated private network prevents outside actors from directly accessing the GraphQL API and limits exposure. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63396 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-63396?
- Check whether you run ROOST Coop at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.0.0
Running the service on an authenticated private network prevents outside actors from directly accessing the GraphQL API and limits exposure.
Technical details
The `Query.allOrgs` GraphQL field and `usersWhoCanReviewEveryQueue` field lack authentication checks and are directly accessible via the `/api/v1/graphql` endpoint. An unauthenticated network attacker can exploit this to enumerate all organizations and extract PII including email addresses, user IDs, names, roles, and permissions. The vulnerability is fixed in version 1.0.0 by removing these unauthenticated public queries and implementing proper access controls.
Affected products
- ROOST Coop before 1.0.0
Timeline
- 2026-10-30: disclosed