Roost Coop up to 0.x GraphQL API /api/v1/graphql Query.allOrgs usersWhoCanReviewEveryQueue access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 2.32 |
Summary
A vulnerability, which was classified as problematic, was found in Roost Coop up to 0.x. Affected by this issue is the function Query.allOrgs of the file /api/v1/graphql of the component GraphQL API. Such manipulation of the argument usersWhoCanReviewEveryQueue leads to access control.
This vulnerability is uniquely identified as CVE-2026-63396. The attack can be launched remotely. No exploit exists.
You should upgrade the affected component.
Details
A vulnerability was found in Roost Coop up to 0.x. It has been rated as problematic. Affected by this issue is the function Query.allOrgs of the file /api/v1/graphql of the component GraphQL API. The manipulation of the argument usersWhoCanReviewEveryQueue with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality. CVE summarizes:
Coop is an open source review and moderation tool from ROOST. Prior to 1.0.0, an unauthenticated actor can query `Query.allOrgs` through `/api/v1/graphql` on a publicly accessible deployment and obtain data for all organizations, including organization IDs, names, email addresses, website URLs and on-call alert email addresses. The `usersWhoCanReviewEveryQueue` field also exposes reviewing users' IDs, email addresses, first and last names, roles, permissions and creation dates. Running the service on an authenticated private network prevents outside actors from directly querying the GraphQL API. This issue is fixed in version 1.0.0.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-63396 since 07/16/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1068.
Upgrading to version 1.0.0 eliminates this vulnerability.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Coop 1.0.0
Timeline
07/16/2026 CVE reserved10/30/2026 Advisory disclosed
10/30/2026 VulDB entry created
10/31/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CNA: GitHub_M
CVE: CVE-2026-63396 (🔒)
GCVE (CVE): GCVE-0-2026-63396
GCVE (VulDB): GCVE-100-429452
Entry
Created: 10/31/2026 00:04Changes: 10/31/2026 00:04 (70)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.