CVE-2025-71388 stoatchat CVE debrief

Who should care

Users and administrators of stoatchat (delta/Revolt) versions from 20241213-1 before 20250210-1 should be aware of this vulnerability and take immediate action to update to version 20250210-1 (0.8.2) or later. Additionally, users with ViewChannel permission on channels should be cautious of potential exploitation and review channel permissions to prevent unauthorized access.

Technical summary

The vulnerability exists in the webhook fetch endpoint, which incorrectly checks for ViewChannel permission instead of ManageWebhooks permission. This allows users with read-only access to channels to retrieve webhook tokens, which can be used to send arbitrary messages to the channel, bypassing channel permissions. The vulnerability was introduced due to a flawed permission check in the webhook fetch endpoint, allowing unauthorized access to webhook tokens.

Defensive priority

High

Recommended defensive actions

• Update stoatchat (delta/Revolt) to version 20250210-1 (0.8.2) or later
• Restrict ViewChannel permission to prevent exploitation
• Monitor channel activity for suspicious messages
• Rotate webhook tokens for affected channels
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record was published on 2026-07-16T13:16:24.193Z and has not been modified since then. The NVD entry is currently Deferred. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the vendor. The vulnerability exists in stoatchat (delta/Revolt) versions from 20241213-1 before 20250210-1, and users should be cautious of potential exploitation.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.