# CVE-2026-116680: Homebox generic notifier SSRF via HTTP redirect after URL validation


- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-4gp5-59x3-vhhg

## What is CVE-2026-116680?

CVE-2026-116680 is a medium-severity vulnerability in sysadminsmedia homebox, published on 27 Oct 2026. 

### Official description

HomeBox is a home inventory and organization system. Prior to version 0.27.0, Homebox validates generic notifier URLs with ValidateNotifierURL before creation, update, testing, and scheduled delivery, but shoutrrr sends the request through http.DefaultClient.Do without a CheckRedirect policy that revalidates each Location target. An authenticated collection member can configure a permitted notifier host that redirects to loopback, link-local, cloud metadata, or another blocked destination, causing the follow-up request to bypass the product's SSRF policy. The flaw is reachable through POST /api/v1/notifiers/test for immediate requests and through stored notifiers during scheduled maintenance delivery. This issue is fixed in version 0.27.0.

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

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


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

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

## Is CVE-2026-116680 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116680 is a medium-severity vulnerability in sysadminsmedia homebox, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116680 in the wild and no public exploit code.

Affected product: sysadminsmedia homebox. 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-116680/ (Markdown: https://insights.sbomify.com/CVE-2026-116680/index.md)
```

## Sources

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

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