Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8amended

Homer: Hardcoded Default Admin Password 'sipcapture' With No Forced Change on First Login

CVE-2026-62252GHSA-6xp5-7rcx-xfgx

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-20260625091610-b2e942031ff8), 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.

Add to your agent

Affected packages

Sources

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-62252: 0.65% estimated exploitation activity in the next 30 days; percentile 51.32 (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 On every fresh Homer deployment using internal authentication, the bootstrap process automatically creates an admin account with the password sipcapture (stored as a legacy SHA-256 hex hash). There is no first-login forced-change mechanism. Any attacker who reaches the login endpoint immediately gains full administrative access. Details config/config.go lines 858-861: coordinator/services/authbootstrap.go lines 20-71: EnsureBootstrapAdminUser() runs at startup. If no admin user exists, it inserts a row with username=admin, passwordhash=DefaultInternalAuthPasswordHash. No forcechange, no firstlogin flag, no expiry is set. coordinator/services/authbootstraptest.go line 114 confirms the plaintext: passwordhash/password.go lines 36-45: Legacy SHA-256 hex hashes are accepted via legacySHA256HexEqual, so the default credential is functional on any deployment. PoC Impact Use of Hard-coded Credentials (CWE-798). Any attacker who can reach a freshly deployed Homer instance gains…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-6xp5-7rcx-xfgx

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6671

  3. Revision 1 · created ·

    Published from osv record GHSA-6xp5-7rcx-xfgx

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-62252

Advisory: Homer: Hardcoded Default Admin Password 'sipcapture' With No Forced Change on First Login
IDs: CVE-2026-62252, GHSA-6xp5-7rcx-xfgx
Record: https://patchnext.com/advisories/cve-2026-62252 (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-20260625091610-b2e942031ff8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/sipcapture/homer-app: affected < 0.0.0-20260625091610-b2e942031ff8; fixed in 0.0.0-20260625091610-b2e942031ff8

## 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-6671 (OSV record GO-2026-6671 lists affected ranges: Go github.com/sipcapture/homer-app >=0)
- Verified: https://osv.dev/vulnerability/GHSA-6xp5-7rcx-xfgx (OSV record GHSA-6xp5-7rcx-xfgx lists affected ranges: Go github.com/sipcapture/homer-app >=0 <0.0.0-20260625091610-b2e942031ff8 (fixed))
- Verified: https://github.com/advisories/GHSA-6xp5-7rcx-xfgx (GitHub-reviewed advisory GHSA-6xp5-7rcx-xfgx lists affected ranges: Go github.com/sipcapture/homer-app >=0 <0.0.0-20260625091610-b2e942031ff8)

Commands are suggestions: review each one before running it.

Loading voting…