Skip to content
Fencer Intel
high 8.5

CVE-2026-46372 json

SillyTavern: SSRF in SearXNG Search Proxy via Unvalidated baseUrl

published 5mo ago modified 3mo ago also EUVD-2026-33397 , GHSA-qg89-qwwh-5f3j

cvss
8.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known, plus a Nuclei check

Summary

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 1.18.0, SillyTavern 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. This vulnerability is fixed in 1.18.0.

Patch / fix

  • npm sillytavern 1.18.0
  • sillytavern sillytavern 1.18.0

Is CVE-2026-46372 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.87% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Nuclei template SillyTavern - Server-Side Request Forgery nuclei detection template
  • github.com https://github.com/SillyTavern/SillyTavern/security/advisories/GHSA-qg89-qwwh-5f3j referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
GitHub 3.1 8.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm sillytavern
<1.18.0
1.18.0

Affected products

  • SillyTavern SillyTavern

Classification

Weakness
  • CWE-918 Server-Side Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.