-Commit-Company Raven up to 3.0.0 Legacy Methods raven_message.py channel IDs improper authorization

Summaryinfo

A vulnerability labeled as problematic has been found in -Commit-Company Raven up to 3.0.0. Affected by this vulnerability is the function get_messages_with_dates/get_all_files_shared_in_channel of the file raven/api/raven_message.py of the component Legacy Methods. Such manipulation of the argument channel IDs leads to improper authorization. This vulnerability is documented as CVE-2026-108730. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in -Commit-Company Raven up to 3.0.0. It has been rated as problematic. Affected by this issue is the function get_messages_with_dates/get_all_files_shared_in_channel of the file raven/api/raven_message.py of the component Legacy Methods. The manipulation of the argument channel IDs with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality. CVE summarizes:

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.

The advisory is shared for download at hackmd.io. This vulnerability is handled as CVE-2026-108730 since 10/11/2026. The exploitation is known to be easy. The attack may be launched remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 10/11/2026). The MITRE ATT&CK project declares the attack technique as T1548.002.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• -Commit-Company

Name

• Raven

Version

• 3.0

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion