Quick answers
- Is CVE-2026-34526 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34526 being exploited in the wild.
- How severe is CVE-2026-34526?
- Medium severity, with a CVSS score of 5, published 2 April 2026.
- Which products and versions are affected?
- sillytavern (npm) SEMVER:introduced=0,fixed=1.17.0.
- Is there a fix for CVE-2026-34526?
- Yes. sillytavern (npm): upgrade to 1.17.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34526 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-34526?
- 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.17.0 or later
npm install sillytavern@1.17.0
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in SillyTavern's `src/endpoints/search.js` component. The application attempts to block access to internal addresses using a regular expression that only matches literal dotted-quad IPv4 addresses. This validation fails to account for 'localhost', IPv6 loopback addresses ([::1]), or DNS names that resolve to internal IPs. An authenticated attacker can exploit this to force the server to fetch and return content from internal network resources. The impact is partially mitigated by a secondary check that restricts requests to the default ports 80 and 443. The issue is resolved in version 1.17.0.
Affected products
- SillyTavern SillyTavern < 1.17.0
Identifiers
- CVE-2026-34526
- GHSA-wm7j-m6jm-8797
Timeline
- 2026-03-28: patched: Version 1.17.0 released
- 2026-03-30: advisory: GitHub Security Advisory published
- 2026-04-02: disclosed: CVE-2026-34526 published to NVD