# CVE-2026-59101: AutoBangumi < 3.2.8 - SSRF via /api/v1/setup/test-downloader

> Unauthenticated attackers can exploit an unprotected setup endpoint to perform Server-Side Request Forgery, probing internal networks and leaking information.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-p8rr-9cvg-cx5j

## What is CVE-2026-59101?

CVE-2026-59101 is a medium-severity server-side request forgery vulnerability in EstrellaXD Auto_Bangumi, published on 2 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AutoBangumi before 3.2.8 contains a server-side request forgery (SSRF) vulnerability that allows unauthenticated remote attackers to probe internal network services by supplying arbitrary host values to an unprotected setup endpoint. Attackers can send requests to the POST /api/v1/setup/test-downloader endpoint during the initial setup window, causing the server to issue HTTP GET requests to internal or reserved addresses and leak information through echoed connection-error messages.

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

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


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

No fix has been published for CVE-2026-59101 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-59101 being exploited?

There is no known exploitation of CVE-2026-59101 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59101 is a medium-severity server-side request forgery vulnerability in EstrellaXD Auto_Bangumi, published on 2 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59101 in the wild and no public exploit code.

Affected product: EstrellaXD Auto_Bangumi. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-59101/ (Markdown: https://insights.sbomify.com/CVE-2026-59101/index.md)
```

## Sources

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

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