# CVE-2026-108731: Raven 2.0.0 through 3.0.0 Missing Authorization via join_workspace Invite-Only Bypass

> Authenticated users can bypass invite-only restrictions to join public workspaces, allowing unauthorized reading and posting in channels.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-9xc3-m4r3-v8qc

## What is CVE-2026-108731?

CVE-2026-108731 is a medium-severity missing authorization vulnerability in The-Commit-Company raven, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Raven 2.0.0 through 3.0.0 contains a missing authorization vulnerability that allows authenticated users to join invite-only Public workspaces by ignoring the can_only_join_via_invite setting. Attackers with the Raven User role can call the join_workspace method to become persistent members, reading and posting in Public and Open channels.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-108731?


## How do I fix CVE-2026-108731?

No fix has been published for CVE-2026-108731 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-108731 being exploited?

There is no known exploitation of CVE-2026-108731 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108731 and fix it if it is affected.

What it is: CVE-2026-108731 is a medium-severity missing authorization vulnerability in The-Commit-Company raven, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108731 in the wild and no public exploit code.

Affected product: The-Commit-Company raven. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-108731/ (Markdown: https://insights.sbomify.com/CVE-2026-108731/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-108731
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-108731
- OSV: https://osv.dev/vulnerability/CVE-2026-108731

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-108731/
Summaries are generated and may contain mistakes; the official description above is the record.