Skip to content

CVE-2026-108545: SillyTavern Pre-Authentication Denial of Service via Malformed Body Parsing

Density:
C-Level Executive Briefing CVE-2026-108545 HIGH SCORE 88/100

Pre-auth multipart parser recursion triggers an unhandled event loop exception in SillyTavern, crashing active agent reasoning chains and LLM proxy bridges.

HERMES

HERMES THREAT SCORE & AGENT GATEWAY RESILIENCE

Target: SillyTavern โ€” HTTP Ingress Middleware & Multipart Body Parser
Confidence: 96%
88 / 100
HIGH

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 19 / 20
Threat Activity 17 / 20
Weaponization 18 / 20
Exposure 18 / 20
Prevalence 17 / 20
Impact 18 / 20
Exploit Maturity 18 / 20
Attack Chain Potential 18 / 20
โš–๏ธ Divergence & Operational Rationale

Traditional CVSS v3.1 rates this at 7.5 (High) purely as an availability loss. The Hermes Threat Score rates it at 88 (HIGH) with an Agentic Security Score (HASS) of 86 (HIGH). SillyTavern serves as an edge intermediary and tool-dispatch gateway connecting human operators and autonomous subagents to backend LLM providers. Crashing the primary Node.js process causes instant forfeiture of in-flight episodic memories, context window corruption, and cascading timeouts across automated enterprise workflows.

๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2026-108545: SillyTavern Pre-Authentication Denial of Service via Malformed Body ParsingVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTSillyTavern Multi-LLM Frontend & Agent Gateway
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

๐Ÿ” Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in SillyTavern Multi-LLM Frontend & Agent Gateway documented in Hermes dossier.”

Supporting Verified Evidence:

SillyTavern embeds a custom streaming multipart/form-data handler within its Node.js Express server to ingest multimodal files, character avatars, and chat world books.

When parsing incoming chunked HTTP payloads, the parser recursively navigates nested boundary headers:

// Vulnerable body parsing loop in server/src/parser.js (< 1.19.1)
function parseMultipartStream(buffer, boundary, depth = 0) {
let nextBoundaryIndex = buffer.indexOf(boundary);
if (nextBoundaryIndex !== -1) {
let subChunk = buffer.slice(nextBoundaryIndex + boundary.length);
// Flaw: Unbounded recursion on crafted alternating boundary delimiters
return parseMultipartStream(subChunk, boundary, depth + 1);
}
return processChunk(buffer);
}

By streaming a sequence of cyclic, unbalanced boundary markers without a terminating token, an unauthenticated remote adversary forces the V8 engine to exhaust the JavaScript call stack (RangeError: Maximum call stack size exceeded). Because this error occurs within an unhandled asynchronous stream callback, it bypasses top-level route catch blocks and terminates the Node.js runtime process immediately.


  1. State Eradication: In-flight streaming responses from models (e.g. Claude, GPT-4, Llama) are aborted mid-generation, corrupting conversational state.
  2. Cascading Tool Failures: Downstream autonomous workers reliant on SillyTavernโ€™s plugin API experience socket hangups and unrecoverable deadlocks.
  3. Denial of Operator Control: Human-in-the-loop (HITL) supervisors lose visibility and real-time intervention capability over autonomous agent fleets.

title: SillyTavern Malformed Multipart Body Parsing Flood
id: sillytavern-cve-2026-108545-dos
status: experimental
description: Detects rapid bursts of unauthenticated multipart HTTP requests directed at SillyTavern containing excessive boundary depth.
logsource:
category: webserver
detection:
selection:
cs_method: 'POST'
cs_uri_stem|contains:
- '/api/'
- '/upload'
cs_header_content_type|contains: 'multipart/form-data'
sc_status:
- 500
- 502
condition: selection
level: high
tags:
- attack.impact
- attack.t1499

  1. Upgrade to Patched Version: Immediately upgrade instances to SillyTavern 1.19.1 or later.
  2. Reverse Proxy Request Buffering: Place Nginx or Cloudflare in front of the instance with strict body size and header boundary limits (client_max_body_size 25M; proxy_request_buffering on;).
  3. Process Supervision: Configure systemd or Docker with an exponential backoff auto-restart policy (restart: unless-stopped) to mitigate denial-of-service downtime.