Raven 2.0.0 through 3.0.0 contains a missing authorization vulnerability in legacy methods in raven/api/raven_message.py that skip the workspace membership check. Authenticated non-members can call get_messages_with_dates or get_all_files_shared_in_channel with predictable channel IDs to read Public channel history and Open/Public channel file metadata across workspaces.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 2
- StatusReceived → DeferredNVD modified 2026-10-16 19:18
- First seenCVSS 5.3NVD modified 2026-10-13 14:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 6
- https://github.com/The-Commit-Company/raven
- https://github.com/The-Commit-Company/raven/blob/a732e10f9c8b2ab3446038396e3eea763da617e7/raven/api/raven_message.py#L580-L595
- https://github.com/The-Commit-Company/raven/blob/a732e10f9c8b2ab3446038396e3eea763da617e7/raven/permissions.py#L165-L170
- https://hackmd.io/@haind/frappe-raven-legacy-endpoints-workspace-isolation-bypass
- https://www.vulncheck.com/advisories/raven-2.0.0-through-3.0.0-missing-authorization-via-legacy-message-and-file-apis
- https://hackmd.io/@haind/frappe-raven-legacy-endpoints-workspace-isolation-bypass