Quick answers
- Is CVE-2026-46372 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46372 being exploited in the wild.
- How severe is CVE-2026-46372?
- High severity, with a CVSS score of 8.5, published 29 May 2026.
- Which products and versions are affected?
- sillytavern (npm) <= 1.17.0, SEMVER:introduced=0,fixed=1.18.0.
- Is there a fix for CVE-2026-46372?
- Yes. sillytavern (npm): upgrade to 1.18.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-46372 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-46372?
- Check whether you run sillytavern (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- sillytavern (npm): upgrade to 1.18.0 or later
npm install sillytavern@1.18.0
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in the `/api/search/searxng` route within `src/endpoints/search.js`. The endpoint accepts a user-provided `baseUrl` parameter and uses it to construct outbound HTTP requests using the `fetch()` API without performing validation against an allowlist, IP ranges, or schemes. An authenticated attacker with low privileges can provide a loopback (127.0.0.1) or internal network address as the `baseUrl`. The server will then fetch the content from the internal target and return the response body to the attacker. This can be used to bypass network firewalls and access internal metadata services, administrative interfaces, or other private network resources. The issue is addressed in version 1.18.0 by the introduction of a configurable private request whitelisting filter.
Affected products
- SillyTavern SillyTavern <= 1.17.0
Identifiers
- CVE-2026-46372
- GHSA-qg89-qwwh-5f3j
Timeline
- 2026-05-18: advisory: GitHub Security Advisory published
- 2026-05-29: disclosed: CVE published to NVD
- 2026-05-29: patched: Vulnerability fixed in version 1.18.0