{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-55473 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-55473 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-55473 is a medium-severity server-side request forgery vulnerability in sysadminsmedia homebox, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-55473 and fix it if it is affected.\n\nWhat it is: CVE-2026-55473 is a medium-severity server-side request forgery vulnerability in sysadminsmedia homebox, published on 21 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-55473 in the wild and no public exploit code.\n\nAffected product: sysadminsmedia homebox. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-55473/ (Markdown: https://insights.sbomify.com/CVE-2026-55473/index.md)","id":"CVE-2026-55473","markdown":"https://insights.sbomify.com/CVE-2026-55473/index.md","name":"CVE-2026-55473","record":{"aliases":["GHSA-r9pf-rg22-655m"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"HomeBox inventory system","requires_auth":"low_privilege","summary":"Authenticated users can bypass SSRF protections via NAT64 prefixes to access cloud metadata or internal hosts, disclosing sensitive credentials.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Server-side request forgery in homebox","id":"CVE-2026-55473","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Snipe-IT: Directory traversal in displaySig","id":"CVE-2026-55474"},"packages":[],"prev":{"headline":"Snipe-IT: API Location Creation Bypasses FMCS Parent-Child Company Boundary Validation","id":"CVE-2026-55472"},"products":["homebox"],"published":"2026-09-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-29","vendors":["sysadminsmedia"]},"summary":"Authenticated users can bypass SSRF protections via NAT64 prefixes to access cloud metadata or internal hosts, disclosing sensitive credentials.","url":"https://insights.sbomify.com/CVE-2026-55473/"}