Quick answers
- Is CVE-2026-63399 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-63399 being exploited in the wild.
- How severe is CVE-2026-63399?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- ROOST Coop prior to 1.0.0.
- Is there a fix for CVE-2026-63399?
- Yes: fixed in 1.0.0. Until then: Run the Coop service on an authenticated private network to prevent unauthenticated access to the GraphQL API. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-63399 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-63399?
- 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
Run the Coop service on an authenticated private network to prevent unauthenticated access to the GraphQL API.
Technical details
The GraphQL Mutation.createOrg operation was exposed without authentication checks, allowing unauthenticated actors to invoke it. Combined with the lack of rate limiting, this could enable database exhaustion attacks. The vulnerability is fixed by removing the unauthenticated public mutation and enforcing proper authentication controls on organization creation.
Affected products
- ROOST Coop prior to 1.0.0
Timeline
- 2026-10-30: disclosed
- 2026-06-04: patched: Fix merged in commit b29242f (prior to advisory date)