Message disclosure via missing history check
Published Aug 16, 2026 · Updated Aug 16, 2026
Authorization bypass in Stoat before 0.15.0 allows remote authenticated users to read message content via single-message fetch requests. In the delta backend's message_fetch route, the handler checks only ViewChannel before returning a message by ID, while sibling history routes require ReadMessageHistory and the underlying Reference::as_message fetch adds no further authorization. Exposure requires a channel configuration that grants ViewChannel but denies ReadMessageHistory; default settings grant both together, but affected members can still use reachable IDs such as last_message_id or reply references to read older content.
Summary
What happened
Authorization bypass in Stoat before 0.15.0 allows remote authenticated users to read message content via single-message fetch requests. In the delta backend's message_fetch route, the handler checks only ViewChannel before returning a message by ID, while sibling history routes require ReadMessageHistory and the underlying Reference::as_message fetch adds no further authorization. Exposure requires a channel configuration that grants ViewChannel but denies ReadMessageHistory; default settings grant both together, but affected members can still use reachable IDs such as last_message_id or reply references to read older content.
The record
- CVE
- CVE-2026-73059
- Published
- Aug 16, 2026
- Updated
- Aug 16, 2026
- Vendor
- Revolt Platforms Ltd
- Product
- Stoat Backend
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 16, 2026CVE publishedPublication date reported by the CVE source.
- Aug 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.15.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Authenticated single-message fetch proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo