Homer: Complete Authentication Bypass When coordinator.jwt.secret Is Empty (Default)
CVE-2026-62253GHSA-rqcc-94gv-wjm9
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/sipcapture/homer-app 0.0.0-20260625093330-5e90809657c9), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/sipcapture/homer-app
- Affected
- < 0.0.0-20260625093330-5e90809657c9
- Fixed in
- 0.0.0-20260625093330-5e90809657c9
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6673 lists affected ranges: Go github.com/sipcapture/homer-app >=0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-rqcc-94gv-wjm9 lists affected ranges: Go github.com/sipcapture/homer-app >=0 <0.0.0-20260625093330-5e90809657c9 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-rqcc-94gv-wjm9 lists affected ranges: Go github.com/sipcapture/homer-app >=0 <0.0.0-20260625093330-5e90809657c9
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-62253: 0.54% estimated exploitation activity in the next 30 days; percentile 45.29 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary Both JWT middleware functions (JWTMiddleware and JWTMiddlewareV4) immediately return next(c) when jwtSecret == "". The JWT secret defaults to an empty string. On a default installation, all protected API endpoints under /api/v1, /api/v3, and /api/v4 are completely unauthenticated. Details coordinator/handlers/auth.go lines 298-304: coordinator/handlers/authv4helpers.go lines 177-182: coordinator/coordinator.go lines 315-317: config/config.go line 845: Secret field struct tag has default:"". The example config ships a placeholder value, but the Go struct default (used when no config is provided) is empty. PoC Impact Missing Authentication for Critical Function (CWE-306). On a default Homer installation with no JWT secret configured, every admin API endpoint is completely unauthenticated. Attackers can read/write all configuration, users, database connections, and stored VoIP call data. Fix Fail closed: if JWT.Secret is empty at startup, abort with a fatal error requiring the…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-rqcc-94gv-wjm9
- Revision 2 · amended ·
Amended from osv record GO-2026-6673
- Revision 1 · created ·
Published from osv record GHSA-rqcc-94gv-wjm9
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-62253 Advisory: Homer: Complete Authentication Bypass When coordinator.jwt.secret Is Empty (Default) IDs: CVE-2026-62253, GHSA-rqcc-94gv-wjm9 Record: https://patchnext.com/advisories/cve-2026-62253 (revision 3, source checked 26 Oct 2026, 15:29 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/sipcapture/homer-app 0.0.0-20260625093330-5e90809657c9. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/sipcapture/homer-app: affected < 0.0.0-20260625093330-5e90809657c9; fixed in 0.0.0-20260625093330-5e90809657c9 ## Suggested inspection (read-only) - Go github.com/sipcapture/homer-app: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/sipcapture/homer-app. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GO-2026-6673 (OSV record GO-2026-6673 lists affected ranges: Go github.com/sipcapture/homer-app >=0) - Verified: https://osv.dev/vulnerability/GHSA-rqcc-94gv-wjm9 (OSV record GHSA-rqcc-94gv-wjm9 lists affected ranges: Go github.com/sipcapture/homer-app >=0 <0.0.0-20260625093330-5e90809657c9 (fixed)) - Verified: https://github.com/advisories/GHSA-rqcc-94gv-wjm9 (GitHub-reviewed advisory GHSA-rqcc-94gv-wjm9 lists affected ranges: Go github.com/sipcapture/homer-app >=0 <0.0.0-20260625093330-5e90809657c9) Commands are suggestions: review each one before running it.
Loading voting…