CVE-2026-55473

HomeBox: Notifier SSRF guard misses NAT64 prefixes (64:ff9b::/96, 64:ff9b:1::/48) — generic:// URL reaches cloud metadata on NAT64 egress

Published Sep 21, 2026 CVSS 4.0 · 6 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The notifier validation in HomeBox fails to examine IPv4 addresses that are embedded within the NAT64 prefixes 64:ff9b::/96 and 64:ff9b:1::/48. When an authenticated user submits a generic:// notifier, the gateway can convert the IPv6 destination to an internal IPv4 endpoint such as the cloud metadata service, localhost, or other private hosts. The POST endpoints /v1/notifiers and /v1/notifiers/test then return delivery results, allowing Shoutrrr to expose the fetched data. Consequently, an attacker can obtain temporary credentials or sensitive internal information, representing a data confidentiality breach.

Affected Systems

All HomeBox installations from versions earlier than 0.26.0 that are configured to egress via NAT64/DNS64 are impacted. The vulnerability exists within the default-on BlockBogonNets and BlockCloudMetadata SSRF checks located in backend/internal/sys/validate/notifier_url.go. Any user who can authenticate and issue POST requests to the notifier endpoints can exploit the flaw.

Risk and Exploitability

The CVSS score of 6 indicates a medium severity. The EPSS score is not available, so the likelihood of exploitation is presently unknown. HomeBox is not listed in the CISA KEV catalog. An attacker needs network access to the instance, an authenticated session, and the ability to submit a notifier; under those conditions the vulnerability can be exercised remotely.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade HomeBox to version 0.26.0 or later, which corrects the SSRF guard.
  • If an upgrade is not possible, configure a firewall or NAT64 policy to block outbound requests that resolve to internal IPv4 addresses such as 169.254.169.254 or localhost during notifier processing.
  • Consider disabling the generic:// scheme for notifier URLs in the application configuration to prevent the formation of potentially harmful requests.

Generated by OpenCVE AI on September 21, 2026 at 19:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Sysadminsmedia
Sysadminsmedia homebox
Vendors & Products Sysadminsmedia
Sysadminsmedia homebox
Type Values Removed Values Added
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.
Title HomeBox: Notifier SSRF guard misses NAT64 prefixes (64:ff9b::/96, 64:ff9b:1::/48) — generic:// URL reaches cloud metadata on NAT64 egress
Weaknesses CWE-918
References
Metrics cvssV4_0

{'score': 6, 'vector': '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'}

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Sep 29, 2026, 2:14 PM
Reserved
Jun 16, 2026, 10:10 PM
Status
Deferred
Published
Sep 21, 2026, 6:17 PM
Modified
Sep 29, 2026, 3:17 PM