Skip to main content
VulnerabilityPublished

CVE-2026-123351: sysadminsmedia homebox · Improper Input Validation

Affects sysadminsmedia homeboxSource CVE Database V5

0
Compare

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

Data as of 17 Nov 2026, 19:49 UTC

CVSS 3.1 base score
4.7Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.14.7
Patch
Available – fixed in 0.27.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 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 16 Nov 2026.

What to do

Upgrade sysadminsmedia homebox to 0.27.0.

Affected software

ProductAffectedFixed in
sysadminsmediahomeboxAffected
  • <0.27.0
Fixed in
  • 0.27.0

Description

HomeBox is a home inventory and organization system. Prior to 0.27.0, the unauthenticated GET /swagger/doc.json endpoint copies the client-supplied X-Forwarded-Host header into the OpenAPI host field without requiring a trusted proxy or validating the value. An attacker can therefore make the served OpenAPI document direct Swagger UI Try it out requests to an attacker-controlled host. When a shared cache or CDN stores and serves that poisoned document to an authenticated user, Swagger UI sends the user's API requests and bearer token to the attacker, enabling disclosure and modification of the user's HomeBox data. Without a shared cache, the attacker can affect only the attacker's own response. This issue is fixed in version 0.27.0.

References

Community reviews

Loading reviews…