stoatchat up to 0.14.x Message Fetch permission

Summaryinfo

A vulnerability classified as problematic has been found in stoatchat up to 0.14.x. This affects an unknown part of the component Message Fetch. Performing a manipulation results in permission. This vulnerability was named CVE-2026-73059. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in stoatchat up to 0.14.x. It has been classified as problematic. This affects some unknown processing of the component Message Fetch. The manipulation with an unknown input leads to a permission vulnerability. CWE is classifying the issue as CWE-275. This is going to have an impact on confidentiality. The summary by CVE is:

stoatchat before 0.15.0 contains a permission bypass vulnerability in the message_fetch route that checks only ViewChannel permission instead of requiring ReadMessageHistory. Attackers with ViewChannel access but ReadMessageHistory denied can retrieve individual message content by ID, bypassing the intended history restriction enforced by bulk read routes.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-73059 since 08/10/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1222 for this issue.

Upgrading to version 0.15.0 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Chat Software

Name

• stoatchat

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6
• 0.7
• 0.8
• 0.9
• 0.10
• 0.11
• 0.12
• 0.13
• 0.14

Website

• Product: https://github.com/stoatchat/stoatchat/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion