CVE-2026-63399: roostorg coop advisory

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

What it is

Coop is an open source review and moderation tool from ROOST. Prior to 1.0.0, the `GraphQL` `Mutation.createOrg` operation allows an unauthenticated actor to create arbitrary organizations on a publicly accessible instance. In addition to creating noise in the logs, the lack of rate limiting could potentially lead to database exhaustion. 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.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-30).

Weakness: CWE-306: Missing Authentication for Critical Function; CWE-799: Improper Control of Interaction Frequency

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality low, integrity low, availability low. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: partial.

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 4 references on Exploit Observer

Live scores

EPSS: 0.003
low predicted chance of attack
VEDAS: 0.985
strong exploit evidence
On CISA KEV: Not listed
Detection rule: Suricata

Who is affected

Product	Affected	Not affected
roostorg coop	version < 1.0.0	Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-63399 Coop - Unauthenticated GraphQL Organization Creation. Add them to your Suricata rule set and reload.

Show the rules

suricata

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-63399 Coop - Unauthenticated GraphQL Organization Creation"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/api/v1/graphql"; nocase; fast_pattern; http.request_body; content:"createOrg"; nocase; classtype:web-application-attack; reference:cve,CVE-2026-63399; reference:url,https://www.exploit.observer/?keyword=CVE-2026-63399&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=coop&match=exact; sid:1103007; rev:1;)

CVE-2026-63399.rules on GitHub

References

Other references

https://github.com/roostorg/coop/security/advisories/GHSA-jcph-g6qv-g475 (x_refsource_CONFIRM)
https://github.com/roostorg/coop/pull/699 (x_refsource_MISC)
https://github.com/roostorg/coop/commit/b29242f12f5acca0ac26116c30be9da77c15d93c (x_refsource_MISC)
https://github.com/roostorg/coop/releases/tag/1.0.0 (x_refsource_MISC)

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.