# CVE-2026-47170: Garlic-Hub: SSRF vulnerability in uploadFromUrl endpoint

> Authenticated users can trigger server-side requests to internal services, enabling port scanning and data retrieval via the uploadFromUrl endpoint.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/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:** No
- **Published:** 11 Jun 2026
- **Updated:** 13 Jun 2026
- **Also known as:** GHSA-x24v-76hr-989r

## What is CVE-2026-47170?

CVE-2026-47170 is a high-severity server-side request forgery vulnerability in garlic-signage garlic-hub, published on 11 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Garlic-Hub manages digital signage network — devices, content, and playlists — from a single self-hosted interface. Prior to version 1.1, authenticated users can cause the server to issue arbitrary HTTP requests to internal services via the uploadFromUrl endpoint. This allows internal port scanning, service fingerprinting, and retrieval of internal HTTP responses which are stored in the publicly accessible media pool. This issue has been patched in version 1.1.

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

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


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

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

## Is CVE-2026-47170 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-47170 is a high-severity server-side request forgery vulnerability in garlic-signage garlic-hub, published on 11 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47170 in the wild and no public exploit code.

Affected product: garlic-signage garlic-hub. 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-47170/ (Markdown: https://insights.sbomify.com/CVE-2026-47170/index.md)
```

## Sources

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

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