Vulnerability in github.com/sipcapture/homer-app (CVE-2026-62253)
Summary
Vulnerability in github.com/sipcapture/homer-app (CVE-2026-62253). Successful exploitation can lead to full system takeover. Exploitable via JWTMiddleware. Mitigation: upgrade to 0.0.0-20260625093330-5e90809657c9 or later.
Original description
The description as published by the source.
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:
func (h *Auth) JWTMiddleware() echo.MiddlewareFunc {
return func(next echo.HandlerFunc) echo.HandlerFunc {
return func(c echo.Context) error {
if h.jwtSecret == "" {
return next(c) // bypass — no validation performed
}
coordinator/handlers/auth_v4_helpers.go lines 177-182:
func (h *Auth) JWTMiddlewareV4() echo.MiddlewareFunc {
return func(next echo.HandlerFunc) echo.HandlerFunc {
return func(c echo.Context) error {
if h.jwtSecret == "" {
return next(c) // same bypass
coordinator/coordinator.go lines 315-317:
if c.config.JWT.Secret != "" {
protected.Use(authHandler.JWTMiddleware()) // middleware not even registered when secret is empty
}
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
# On a default Homer installation (no JWT secret configured), all protected routes are open:
curl http:///api/v3/users
# Returns f…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-62253 has been found in github.com/sipcapture/homer-app.
Attackers can target a specific entry point like JWTMiddleware over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade github.com/sipcapture/homer-app to 0.0.0-20260625093330-5e90809657c9 or later.
If unsure, ask your IT team or search "github.com/sipcapture/homer-app CVE-2026-62253" on the vendor's site.
CVE-2026-62253 (github.com/sipcapture/homer-app) — CWE-306 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: JWTMiddleware / JWTMiddlewareV4 / Secret / JWT.Secret
Patched: 0.0.0-20260625093330-5e90809657c9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-306) exists in github.com/sipcapture/homer-app. Attackers reach the vulnerable code path via JWTMiddleware without authentication.
Check the vendor advisory for the affected versions of github.com/sipcapture/homer-app. Attack surface: JWTMiddleware / JWTMiddlewareV4 / Secret / JWT.Secret.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 0.0.0-20260625093330-5e90809657c9.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/sipcapture/homer-app' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/sipcapture/homer-app' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/sipcapture/homer-appを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/sipcapture/homer-app to 0.0.0-20260625093330-5e90809657c9ステージング環境で 0.0.0-20260625093330-5e90809657c9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。