CVE-2026-34524 | SillyTavern up to 1.16.x Chat Endpoint secrets.json avatar_url path traversal

VDB-354965 · CVE-2026-34524 · GCVE-0-2026-34524 SILLYTAVERN UP TO 1.16.X CHAT ENDPOINT SECRETS.JSON AVATAR_URL PATH TRAVERSAL HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.7 $0-$5k 0.85+ Summaryinfo A vulnerability identified as critical has been detected in SillyTavern up to 1.16.x. The affected element is an unknown function of the file secrets.json of the component Chat Endpoint. The manipulation of the argument avatar_url leads to path traversal. This vulnerability is referenced as CVE-2026-34524. The attack can only be performed from a local environment. No exploit is available. You should upgrade the affected component. Detailsinfo A vulnerability was found in SillyTavern up to 1.16.x and classified as critical. This issue affects some unknown functionality of the file secrets.json of the component Chat Endpoint. The manipulation of the argument avatar_url with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, integrity, and availability. The summary by CVE is: SillyTavern is a locally installed user interface that allows users to interact with text generation large language models, image generation engines, and text-to-speech voice models. Prior to version 1.17.0, a path traversal vulnerability in chat endpoints allows an authenticated attacker to read and delete arbitrary files under their user data root (for example secrets.json and settings.json) by supplying avatar_url="..". This issue has been patched in version 1.17.0. The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-34524 since 03/30/2026. The exploitation is known to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1006 for this issue. By approaching the search of inurl:secrets.json it is possible to find vulnerable targets with Google Hacking. Upgrading to version 1.17.0 eliminates this vulnerability. Productinfo Name SillyTavern Version 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 1.11 1.12 1.13 1.14 1.15 1.16 Website Product: https://github.com/SillyTavern/SillyTavern/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 6.8 VulDB Meta Temp Score: 6.7 VulDB Base Score: 5.3 VulDB Temp Score: 5.1 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 8.3 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Path traversal CWE: CWE-22 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: Yes Availability: 🔒 Status: Not defined Google Hack: 🔒 Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: SillyTavern 1.17.0 Timelineinfo 03/30/2026 CVE reserved 04/02/2026 +3 days Advisory disclosed 04/02/2026 +0 days VulDB entry created 04/02/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-34524 (🔒) GCVE (CVE): GCVE-0-2026-34524 GCVE (VulDB): GCVE-100-354965 Entryinfo Created: 04/02/2026 19:38 Changes: 04/02/2026 19:38 (65) Complete: 🔍 Cache ID: 99:7DD:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸