CVE-2026-108545 SillyTavern CVE debrief

Who should care

Defenders responsible for SillyTavern deployments, especially those exposed to untrusted networks, should assess and prioritize remediation of this high-severity vulnerability. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify affected versions, assess exposure, and implement mitigations or compensating controls.

Why it matters

CVE-2026-108545 is a high-severity denial-of-service vulnerability in SillyTavern versions 1.12.13 through 1.19.0, allowing unauthenticated remote attackers to exhaust resources. Defenders should prioritize verification and remediation, especially in exposed environments.

• Denial of service due to resource exhaustion
• Potential for significant memory and CPU utilization
• Need for verification of affected versions and exposure
• Priority for remediation and compensating controls

Technical summary

The vulnerability is caused by the body-parser middleware processing large or compressed JSON or urlencoded bodies up to 500 MB, optionally in parallel, which can exhaust memory and CPU resources and deny service. This issue affects SillyTavern versions 1.12.13 through 1.19.0. The vulnerability can be mitigated by implementing authentication and whitelist checks before the body-parser middleware, limiting the size of JSON or urlencoded bodies, and monitoring for suspicious traffic patterns. Defenders should prioritize verifying and remediating this vulnerability, especially in environments where SillyTavern is exposed to untrusted networks.

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability, especially in environments where SillyTavern is exposed to untrusted networks.

Recommended defensive actions

• Verify SillyTavern version and assess exposure
• Implement authentication and whitelist checks before body-parser middleware
• Limit the size of JSON or urlencoded bodies
• Monitor for suspicious traffic patterns
• 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 vulnerability is caused by the body-parser middleware processing large or compressed JSON or urlencoded bodies up to 500 MB, optionally in parallel, which can exhaust memory and CPU resources. The evidence for this vulnerability is based on the CVE record and the NVD detail page. However, the exact scope of affected systems and potential impact on specific deployments is not detailed in the available sources. Defenders should verify the affected versions and exposure in their environments.

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.