Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost malicious SVG with extreme viewBox dimensions
-
DeliverySend concurrent HTTP requests to stoatchat proxy endpoint
-
ExploitProxy fetches and allocates memory per declared SVG dimensions
-
ExecutionConcurrent allocations accumulate without bounds across replicas
-
PersistMemory exhausted
-
ImpactService crash and denial of service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The stoatchat proxy endpoint must be network-accessible to the attacker, which the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) confirms requires no authentication, no special configuration beyond a default deployment, and no user interaction. The attacker must be able to host or reference an SVG file with extreme dimension values reachable by the stoatchat proxy - this requires control of an externally reachable URL the proxy will fetch. Effective memory exhaustion across replicas further requires the ability to issue concurrent requests simultaneously, meaning a single sequential request is unlikely to alone exhaust memory. Limiting factors: the attacker must control or access an SVG-hosting URL the proxy will resolve; the concurrent-request requirement introduces operational complexity compared to single-packet exploits; and exploitation impact is limited to availability with no confidentiality or integrity consequence. |
| Impact | The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N) places this firmly as a remotely exploitable, zero-complexity, no-privilege denial-of-service: the highest tier of DoS risk in terms of reachability and ease. No EPSS score was supplied in the input, so exploitation probability cannot be quantified numerically. No CISA KEV listing was provided, meaning confirmed active exploitation is not established at time of analysis. The attack barrier is low - an attacker only needs to host a malicious SVG and script concurrent HTTP requests - but effective exhaustion across replicas does require volumetric concurrency, adding modest operational overhead. The primary limiting factor for real-world impact is stoatchat's niche deployment footprint; internet-facing stoatchat instances with an unauthenticated proxy endpoint represent the highest-risk population. No conflicting signals were identified between CVSS and the description. |
| Exploit ScenarioDerived | An unauthenticated attacker hosts an SVG file on a public server with viewBox dimensions set to near-integer-maximum values (e.g., width='2000000000' height='2000000000'). The attacker then scripts a tool to issue hundreds of simultaneous HTTP requests to the stoatchat proxy endpoint referencing this SVG URL, causing each replica to allocate memory proportional to the declared dimensions per request. As allocations accumulate across replicas without being bounded or released, available system memory is exhausted and the stoatchat service crashes or becomes unresponsive, constituting a complete denial of service. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 16, 2026
Memory exhaustion denial of service in stoatchat before 0.15.0 allows unauthenticated remote attackers to crash the service by submitting concurrent proxy requests referencing attacker-hosted SVGs with arbitrarily large viewBox width and height values. The proxy endpoint allocates memory proportional to declared SVG dimensions without enforcing any upper bound (CWE-400), and concurrent exploitation amplifies impact across all running replicas simultaneously. No public exploit code or CISA KEV listing has been identified at time of analysis; the CVSS 4.0 score of 8.7 reflects the high availability impact with no confidentiality or integrity component.
RemediationAI
Upgrade stoatchat to version 0.15.0 or later, which introduces dimension validation in the SVG proxy endpoint; this is the primary and recommended fix per the GitHub security advisory at https://github.com/stoatchat/stoatchat/security/advisories/GHSA-x87r-h3mq-7mgr. If an immediate upgrade is not feasible, consider placing the proxy endpoint behind authentication middleware to eliminate unauthenticated access - note this changes the application's intended behavior and may break features for legitimate users. Alternatively, configure a reverse proxy or API gateway in front of stoatchat to enforce per-IP or per-endpoint request rate limits and concurrency caps, reducing the attacker's ability to sustain the concurrent request volume needed for full memory exhaustion - this mitigates impact severity but does not eliminate the root-cause allocation issue. Network-level egress filtering to restrict which external URLs the proxy can fetch would also limit the attacker's ability to serve the malicious SVG from an attacker-controlled host.
Affected VersionsENISA
Affected Packages
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 includes a proxy endpoint that fetches and processes externally hosted SVG files. SVG documents declare rendering dimensions via viewBox, width, and height attributes; a compliant renderer allocates memory proportional to those values for rasterisation or layout computation. CWE-400 (Uncontrolled Resource Consumption) is the root cause: the application imposes no cap on these declared dimensions before allocation, meaning a single SVG can trigger an arbitrarily large allocation. When an attacker issues many concurrent requests - each referencing an SVG with extreme values such as width='2147483647' height='2147483647' - the cumulative unreclaimed allocations across proxy replicas exhaust available system memory. The CPE string cpe:2.3:a:stoatchat:stoatchat:*:*:*:*:*:*:*:* covers all stoatchat versions prior to 0.15.0.
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
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Network-accessible proxy requires no authentication or interaction; impact is availability-only with no scope change, confidentiality, or integrity effect.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
stoatchat before 0.15.0 fails to validate SVG viewBox dimensions in the proxy endpoint, allowing attackers to cause denial of service by memory exhaustion. Attackers can host malicious SVGs with extremely large width and height values and trigger concurrent requests to exhaust available memory across proxy replicas.
Executive ViewAI
stoatchat proxy endpoint (versions before 0.15.0) contains an unauthenticated denial-of-service vulnerability via unbounded memory allocation that can crash the entire service cluster when processing malicious SVG viewBox dimensions. While no public exploit has been identified at time of analysis, the straightforward attack method poses a significant availability risk to dependent business operations. Immediate mitigation is required as no vendor patch is currently available.
No vendor-released patch identified at time of analysis. Implement rate limiting on the proxy endpoint (recommend 10 requests per second per source IP), enforce maximum SVG viewBox dimensions at the validation layer (recommend 10,000 x 10,000 pixels maximum), configure memory usage monitoring with automated service restart triggers at 80% threshold, restrict proxy endpoint access to authenticated users where operationally feasible, and deploy Web Application Firewall rules to block requests containing SVG payloads with excessive viewBox values.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Server-side request forgery in stoatchat before 0.13.5 allows remote unauthenticated attackers to coerce the server into
Unauthenticated remote attackers can use the January media proxy/embed service in stoatchat before 0.15.5 to probe the h
Denial of service in stoatchat (delta) versions before 20250210-1 (0.8.2) lets a remote unauthenticated attacker exhaust
Missing authorization in stoatchat's Subscribe message handler exposes private server membership data to any authenticat
MFA enforcement in Stoatchat before 0.15.5 can be bypassed by an attacker who already holds the victim's password, becau
Server-side request forgery in Stoatchat before 0.14.0 lets unauthenticated, network-accessible attackers reach internal
Webhook token disclosure in stoatchat (the Rust 'delta' backend of the Revolt/stoatchat platform) lets any channel membe
MFA bypass in StoatChat before 0.15.5 allows an authenticated attacker to satisfy the MFA step-up re-authentication chal
Authenticated members of a Stoat Chat deployment can permanently (until restart) disable push notifications and mention
Permission bypass in stoatchat before 0.15.0 allows authenticated users holding only ViewChannel access to read individu
Stoatchat releases prior to 0.15.5 hand unauthenticated remote attackers an account-existence oracle: POST /api/auth/ses
SSRF protection bypass in stoatchat before 0.15.0 exposes loopback-bound services to unauthenticated remote attackers th
EUVD-2026-59943
GHSA-4rgf-ww29-jxx4
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB