# CVE-2026-34526: SillyTavern: Incomplete IP validation in /api/search/visit allows SSRF via localhost and IPv6

> Attackers can bypass IP validation to access internal services via localhost or IPv6, potentially reading sensitive data.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Apr 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-wm7j-m6jm-8797

## What is CVE-2026-34526?

CVE-2026-34526 is a medium-severity server-side request forgery vulnerability in SillyTavern, published on 2 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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 version 1.17.0, in src/endpoints/search.js, the hostname is checked against /^\d+\.\d+\.\d+\.\d+$/. This only matches literal dotted-quad IPv4 (e.g. 127.0.0.1, 10.0.0.1). It does not catch: localhost (hostname, not dotted-quad), [::1] (IPv6 loopback), and DNS names resolving to internal addresses (e.g. localtest.me -> 127.0.0.1). A separate port check (urlObj.port !== '') limits exploitation to services on default ports (80/443), making this lower severity than a fully unrestricted SSRF. This issue has been patched in version 1.17.0.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-34526?

2 open source packages ship an affected version, including sillytavern. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sillytavern` | npm | All versions | 1.17.0 |
| `sillytavern` | npm | All versions | 1.17.0 |

Products: Sillytavern Sillytavern.

## How do I fix CVE-2026-34526?

Upgrade sillytavern to 1.17.0 or later.

## Is CVE-2026-34526 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34526 exists.

## Other vulnerabilities in SillyTavern

- [CVE-2026-34524](https://insights.sbomify.com/CVE-2026-34524/): SillyTavern: Path Traversal in `/api/chats/export` and `/api/chats/delete` allows arbitrary file read/delete within user data root (high 8.3)
- [CVE-2026-34522](https://insights.sbomify.com/CVE-2026-34522/): SillyTavern: Path traversal in `/api/chats/import` allows arbitrary file write outside intended chat directory (high 8.1)
- [CVE-2026-26286](https://insights.sbomify.com/CVE-2026-26286/): SillyTavern has Server-Side Request Forgery (SSRF) via Asset Download Endpoint that Allows Reading Internal Services (high 7.1)
- [CVE-2026-34523](https://insights.sbomify.com/CVE-2026-34523/): SillyTavern: Path traversal allows file existence oracle (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34526 and fix it if it is affected.

What it is: CVE-2026-34526 is a medium-severity server-side request forgery vulnerability in SillyTavern, published on 2 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34526 exists.

Affected packages and fixed versions:
- sillytavern (npm): affected all versions; fixed in 1.17.0
- sillytavern (npm): affected all versions; fixed in 1.17.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34526/ (Markdown: https://insights.sbomify.com/CVE-2026-34526/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34526
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34526
- OSV: https://osv.dev/vulnerability/CVE-2026-34526

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34526/
Summaries are generated and may contain mistakes; the official description above is the record.