Live › vulnerability › CVE-2026-116680
Go to dashboardHomeBox validates notifier URLs against an SSRF policy, but the shoutrrr HTTP client follows redirects without rechecking the target. An authenticated collection member can point a permitted notifier host at a redirect to loopback, link-local, or cloud metadata addresses and make the server request them.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 18:32 UTC. All times on this page are UTC.
Self-hosted HomeBox instances before 0.27.0 that let collection members create or edit notifiers. Exposure needs an account in a collection, and the attacker must control a host that is allowed by the notifier validation and redirects. Instances on managed hosting that enforce network egress controls reduce the reach of metadata and internal targets.
No product ranges from the sources yet.
0.27.0 are affected.0.27.0 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-116680")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.