Skip to main content
VulnerabilityPublished Updated

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

Affects sysadminsmedia homeboxSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.0 Medium : upgrade to 0.26.0 when convenient.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.26.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 5 Nov 2026.

What to do

Upgrade homebox and sysadminsmedia/homebox to 0.26.0.

Affected software

ProductAffectedFixed in
sysadminsmediahomeboxAffected
  • <0.26.0
Fixed in
  • 0.26.0
GitHubsysadminsmedia/homeboxpkg:github/sysadminsmedia/homeboxOther threatsAffected
  • <0.26.0
Fixed in
  • 0.26.0

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

AI-suggested

Upgrade to homebox version 0.26.0 or later, where this SSRF vulnerability is fixed. The vendor advisory confirms the issue is resolved in 0.26.0. No additional mitigations are specified.

Description

HomeBox is a home inventory and organization system. Prior to 0.26.0, the default-on BlockBogonNets and BlockCloudMetadata notifier SSRF protections in backend/internal/sys/validate/notifier_url.go do not inspect IPv4 destinations embedded in the NAT64 prefixes 64:ff9b::/96 and 64:ff9b:1::/48. An authenticated user can submit a generic:// notifier through POST /v1/notifiers or POST /v1/notifiers/test, and on a Homebox instance that egresses through NAT64/DNS64, the gateway can translate an accepted IPv6 destination to cloud metadata, localhost, or another internal IPv4 host. The notifier test path returns delivery result information, and Shoutrrr propagates the response, providing feedback that can disclose retrieved metadata such as temporary credentials. Without NAT64 egress, the crafted IPv6 destination is not routable, but the guard still incorrectly classifies it as safe. This issue is fixed in version 0.26.0.

References

Community reviews

Loading reviews…