# CVE-2026-111720: fish-island-backend through commit 7c61b78 SSRF via /api/web/parse

> Unauthenticated attackers can exploit SSRF in fish-island-backend to access internal services and cloud metadata via the URL parsing endpoint.

- **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:** 16 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-mc35-74mg-3v34

## What is CVE-2026-111720?

CVE-2026-111720 is a medium-severity server-side request forgery vulnerability in lhccong fish-island-backend, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

fish-island-backend through commit 7c61b78 contains an unauthenticated server-side request forgery vulnerability that allows remote attackers to make the server fetch attacker-supplied URLs via the url parameter of GET /api/web/parse. Attackers can target internal hosts, loopback services or cloud metadata endpoints through redirect-following OkHttp requests and read back page titles, meta descriptions and favicons.

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

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


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

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

## Is CVE-2026-111720 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111720 is a medium-severity server-side request forgery vulnerability in lhccong fish-island-backend, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111720 exists.

Affected product: lhccong fish-island-backend. 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-111720/ (Markdown: https://insights.sbomify.com/CVE-2026-111720/index.md)
```

## Sources

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

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