Skip to main content

stoatchat CVE-2026-74869

| EUVDEUVD-2026-60088 HIGH
Missing Authorization (CWE-862)
2026-08-17 VulnCheck GHSA-5cwg-5wjq-gqw2
8.3
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain valid stoatchat account
  2. Delivery
    Enumerate or guess target private server ID
  3. Exploit
    Send crafted Subscribe message with target server ID
  4. Execution
    Receive live UserUpdate event stream
  5. Impact
    Harvest member profiles and presence data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires a valid authenticated session on the target stoatchat instance (PR:L - low-privilege account sufficient, no administrative rights needed). The target must be a private server with members whose data the attacker is not authorized to access. The attacker must know or be able to discover a target server's ID; depending on the application's ID scheme (sequential integers vs. opaque UUIDs), this may or may not require additional reconnaissance. No special configuration, feature flag, or non-default deployment mode is required beyond the standard Subscribe message handler being exposed - which is core functionality. Exploitation is limited to confidentiality (no write or destructive capability), and impacts only data belonging to private servers the attacker does not legitimately belong to.

Impact

The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N) scores 8.3, reflecting network accessibility, low attack complexity, and high confidentiality impact on both the vulnerable system and subsequent systems (private server data contexts). Real-world risk is moderate-to-high for deployments where private server membership or user identity is sensitive - for example, internal enterprise communication tools or communities with privacy expectations. The PR:L requirement (a valid authenticated account) limits exposure to insider threats or compromised accounts rather than unauthenticated external attackers. No EPSS data was provided, and the vulnerability is not listed in the CISA KEV catalog, suggesting exploitation has not yet been observed at scale. The absence of complex preconditions (AC:L, AT:N) means exploitation is trivially automatable once an account is obtained. The primary real-world concern is bulk enumeration: an attacker can systematically harvest membership and presence data across many private servers with a single authenticated session.

Exploit ScenarioDerived

An attacker registers or compromises a low-privilege account on a stoatchat instance, then sends a Subscribe message with the ID of a private server they are not a member of - obtainable through prior reconnaissance or brute-force. The server responds with a live stream of UserUpdate events, allowing the attacker to silently monitor all members' display names, avatars, and online/offline status changes in real time without triggering any membership notification. No public exploit code has been identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 17, 2026

Missing authorization in stoatchat's Subscribe message handler exposes private server membership data to any authenticated user on the platform. By sending a crafted Subscribe message referencing an arbitrary server ID, an authenticated attacker receives a live stream of UserUpdate events - including display names, avatars, and presence status - for members of private servers they have no legitimate access to. No public exploit code has been identified at time of analysis, but the attack is trivially repeatable by any account holder, requiring only knowledge of a target server's ID.

RemediationAI

Upgrade stoatchat to version 0.15.0 or later, which resolves the missing authorization check in the Subscribe message handler. The fix is confirmed available per the vendor security advisory at https://github.com/stoatchat/stoatchat/security/advisories/GHSA-jj3j-9qr7-jgfc. If an immediate upgrade is not feasible, a compensating control is to restrict account creation to trusted users only, reducing the pool of potential attackers with the PR:L foothold required. Additionally, operators can implement server-side rate limiting or anomaly detection on Subscribe message volume per account to flag bulk server enumeration attempts - though this does not prevent a slow, targeted attacker. Neither workaround addresses the root authorization flaw. Audit logs should be reviewed for Subscribe messages referencing server IDs that do not correspond to the sending user's memberships.

Affected VersionsENISA

stoatchat 0 <0.15.0

Affected Packages

euvd stoatchat fix: 0.15.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

stoatchat is a chat application that uses a message-passing protocol (likely WebSocket-based) with typed message handlers. The Subscribe message handler, responsible for establishing real-time event subscriptions to server-scoped topics, is affected by CWE-862 (Missing Authorization): the server accepts a Subscribe message with a caller-supplied server ID and begins delivering member-update events without verifying that the authenticated user holds membership in the referenced server. The flaw is architectural - the authentication layer (confirming identity via PR:L) is decoupled from the authorization layer (confirming entitlement to the resource). CPE cpe:2.3:a:stoatchat:stoatchat:*:*:*:*:*:*:*:* covers all stoatchat versions prior to 0.15.0. The member-update event stream leaks PII-adjacent data: display names, avatars, and real-time status changes.

Know when Stoatchat gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 8.3 HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
vuln.today AI 7.7 HIGH

Network-accessible with low complexity; PR:L because a valid account is required; scope changes since private server data crosses authorization boundaries; C:H for member PII exposure; no integrity or availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
High
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Aug 17, 2026 - 12:01 EUVD
CVE Published
Aug 17, 2026 - 11:04 cve.org
HIGH 8.3

DescriptionCVE.org

stoatchat before 0.15.0 contains a missing authorization vulnerability in the Subscribe message handler that allows authenticated attackers to enumerate members and monitor profile updates of private servers without membership. Attackers can subscribe to any server's member-update topic by sending a Subscribe message with an arbitrary server ID, receiving live UserUpdate events including display names, avatars, and status changes for members they should not have access to.

Executive ViewAI

Why It Matters

A security flaw in Stoatchat allows any employee with a platform account to view private team member information they shouldn't access; no public exploit identified at time of analysis. This could expose internal staffing structures and confidential team membership to unauthorized co-workers. Organizations using Stoatchat for sensitive team communications face immediate risk of unauthorized data exposure.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 82% exploitable
Prevalence
Rare
obscure niche chat application, minimal documented enterprise adoption
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2026-63306 CRITICAL
9.2 Jul 16

Server-side request forgery in stoatchat before 0.13.5 allows remote unauthenticated attackers to coerce the server into

CVE-2026-100676 HIGH
8.8 Sep 26

Unauthenticated remote attackers can use the January media proxy/embed service in stoatchat before 0.15.5 to probe the h

CVE-2025-71377 HIGH
8.7 Jul 16

Denial of service in stoatchat (delta) versions before 20250210-1 (0.8.2) lets a remote unauthenticated attacker exhaust

CVE-2026-73057 HIGH
8.7 Aug 16

Memory exhaustion denial of service in stoatchat before 0.15.0 allows unauthenticated remote attackers to crash the serv

CVE-2026-100678 HIGH
8.3 Sep 26

MFA enforcement in Stoatchat before 0.15.5 can be bypassed by an attacker who already holds the victim's password, becau

CVE-2026-63088 HIGH
7.7 Jul 16

Server-side request forgery in Stoatchat before 0.14.0 lets unauthenticated, network-accessible attackers reach internal

CVE-2025-71388 HIGH
7.6 Jul 16

Webhook token disclosure in stoatchat (the Rust 'delta' backend of the Revolt/stoatchat platform) lets any channel membe

CVE-2026-100679 HIGH
7.1 Sep 26

MFA bypass in StoatChat before 0.15.5 allows an authenticated attacker to satisfy the MFA step-up re-authentication chal

CVE-2026-100675 HIGH
7.1 Sep 26

Authenticated members of a Stoat Chat deployment can permanently (until restart) disable push notifications and mention

CVE-2026-73059 HIGH
7.1 Aug 16

Permission bypass in stoatchat before 0.15.0 allows authenticated users holding only ViewChannel access to read individu

CVE-2026-100677 MEDIUM
6.9 Sep 26

Stoatchat releases prior to 0.15.5 hand unauthenticated remote attackers an account-existence oracle: POST /api/auth/ses

CVE-2026-73058 MEDIUM
6.9 Aug 16

SSRF protection bypass in stoatchat before 0.15.0 exposes loopback-bound services to unauthenticated remote attackers th

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy