Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-100679 Overview
CVE-2026-100679 is a multi-factor authentication (MFA) bypass vulnerability in stoatchat versions prior to 0.15.5. The application fails to validate that MFA tickets belong to the authenticated user. An attacker with their own valid account can obtain an MFA ticket and present it alongside a victim's session token to perform sensitive operations. These operations include disabling Time-based One-Time Password (TOTP), viewing recovery codes, and modifying account security settings without the victim's credentials. The weakness is classified as Authorization Bypass Through User-Controlled Key [CWE-639].
Critical Impact
Attackers who possess a victim's session token can bypass MFA entirely and take over the victim's account by substituting their own MFA ticket.
Affected Products
- stoatchat versions before 0.15.5
Discovery Timeline
- 2026-09-26 - CVE-2026-100679 published to the National Vulnerability Database (NVD)
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-100679
Vulnerability Analysis
The vulnerability resides in stoatchat's MFA validation workflow. When a user initiates a sensitive operation, the server issues an MFA ticket upon successful second-factor verification. The server then accepts that ticket to authorize the follow-up request. The flaw is that the ticket is treated as a bearer token without binding it to the user who completed the MFA challenge.
An attacker completes MFA on their own account and receives a valid ticket. The attacker then submits a request against the victim's account using the victim's session token together with the attacker-owned ticket. The server validates the ticket in isolation and authorizes the sensitive action. This defeats the purpose of MFA for operations such as disabling TOTP or revealing recovery codes.
Root Cause
The root cause is missing authorization between two authentication artifacts. The MFA ticket is not cryptographically or logically tied to the session token or user identifier. The server does not compare the ticket owner against the session owner before authorizing privileged account changes. This matches the pattern described by CWE-639: Authorization Bypass Through User-Controlled Key.
Attack Vector
Exploitation requires network access to the stoatchat API and possession of a victim's session token. Session tokens can be obtained through separate attacks such as cross-site scripting, token theft, or session fixation. The attacker then performs MFA on an account they control, captures the resulting ticket, and replays it in requests scoped to the victim's session. No interaction from the victim is required once the session token is captured. Technical details are documented in the GitHub Security Advisory GHSA-gwg6-q3c3-97cx and the VulnCheck advisory.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-100679
Indicators of Compromise
- MFA tickets being validated against sessions whose user identifier does not match the ticket owner.
- Unexpected disable-TOTP, view-recovery-codes, or security-settings requests originating from IP addresses that differ from the account's historical login IPs.
- Short time gaps between an attacker-controlled account completing MFA and a victim account performing a sensitive security change.
Detection Strategies
- Log and correlate the user_id embedded in MFA tickets with the user_id bound to the session token used in the same request.
- Alert on sensitive endpoints such as TOTP disable, recovery code retrieval, and password reset when the ticket owner and session owner differ.
- Hunt for anomalous sequences where a single source completes MFA on one account and immediately targets another account's security settings.
Monitoring Recommendations
- Instrument the stoatchat API gateway to capture ticket identifiers, session identifiers, and user identifiers for every MFA-protected request.
- Monitor for spikes in failed authorization checks on /mfa and account security endpoints after upgrading to 0.15.5.
- Review audit logs for sensitive account changes performed in the 30 days before patching to identify prior exploitation attempts.
How to Mitigate CVE-2026-100679
Immediate Actions Required
- Upgrade stoatchat to version 0.15.5 or later as the primary remediation.
- Invalidate all active sessions and MFA tickets after upgrading to force re-authentication.
- Audit recent changes to TOTP configuration, recovery codes, and account security settings for signs of unauthorized modification.
- Rotate recovery codes for any account where cross-user MFA ticket activity cannot be ruled out.
Patch Information
The vulnerability is fixed in stoatchat 0.15.5. The patch enforces that each MFA ticket is bound to the authenticated user and rejects any request where the ticket owner does not match the session owner. Refer to the GitHub Security Advisory GHSA-gwg6-q3c3-97cx for commit references and upgrade instructions.
Workarounds
- If immediate upgrade is not possible, add a reverse-proxy or middleware check that compares the user_id claim of the MFA ticket to the session owner and rejects mismatches.
- Restrict access to MFA-protected endpoints to trusted network ranges until the patch is deployed.
- Reduce MFA ticket lifetimes to the minimum operational value to shrink the exploitation window.
# Configuration example: upgrade stoatchat to a fixed version
npm install stoatchat@0.15.5
# or, for container deployments
docker pull stoatchat/stoatchat:0.15.5
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

