VulnerabilityPublished 27 Oct 2026

CVE-2026-116680: sysadminsmedia homebox · Server-Side Request Forgery (SSRF)

Affects sysadminsmedia homeboxSource CVE Database V5

Not known to be exploited · CVSS 6.4 Medium : upgrade to 0.27.0 when convenient.

Data as of 27 Oct 2026, 18:12 UTC

CVSS 3.1 base score

6.4Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 0.27.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade homebox and sysadminsmedia/homebox to 0.27.0.

Affected software

Product	Affected	Fixed in
sysadminsmediahomebox	Affected <0.27.0	Fixed in 0.27.0
GitHubsysadminsmedia/homebox`pkg:github/sysadminsmedia/homebox`Other threats	Affected <0.27.0	Fixed in 0.27.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade HomeBox to version 0.27.0 or later, where this SSRF vulnerability is fixed. No additional mitigation is necessary once the product is updated. If upgrading immediately is not possible, restrict authenticated user permissions to prevent configuration of notifier hosts or disable notifier testing functionality until patched.

Description

HomeBox versions prior to 0.27.0 contain a server-side request forgery (SSRF) vulnerability due to improper handling of HTTP redirects in notifier URL validation. Authenticated users can exploit this by configuring notifier hosts that redirect to restricted internal addresses, bypassing SSRF protections. The issue affects immediate and scheduled notifier requests. It is fixed in version 0.27.0.

Impact

An authenticated user can exploit this vulnerability to cause the server to make unauthorized HTTP requests to internal or otherwise restricted network resources by leveraging redirect-based bypass of SSRF protections. This can lead to limited confidentiality and integrity impacts, such as unauthorized access to internal services or metadata endpoints. The CVSS score is 6.4 (medium severity), reflecting network attack vector, low attack complexity, low privileges required, no user interaction, and partial confidentiality and integrity impact.

Summary

CVE-2026-116680 is a CWE-918 SSRF vulnerability in sysadminsmedia's HomeBox product before version 0.27.0. The product validates notifier URLs using ValidateNotifierURL, but the underlying HTTP client (shoutrrr) sends requests without a CheckRedirect policy that revalidates each redirect target. This allows an authenticated collection member to configure a notifier host that redirects to loopback, link-local, cloud metadata, or other blocked destinations, effectively bypassing SSRF protections. The flaw can be triggered via POST /api/v1/notifiers/test for immediate requests and through stored notifiers during scheduled maintenance delivery. The vulnerability is resolved in version 0.27.0.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Oct 2026, 17:59 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats