Skip to content

← Actionable
High, CVSS 8.1amended

Homer: Authenticated SQL Injection via Unvalidated rawquery Field in /api/v4/statistics/query

CVE-2026-62251GHSA-f46q-3v67-fmm4

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-20260625085520-a7d027dc684b), 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

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
  • CVE-2026-62251: 0.43% estimated exploitation activity in the next 30 days; percentile 37.67 (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 The V4StatisticsQuery handler passes the user-supplied rawquery field directly to DuckDB without calling the sqlvalidator.ValidateRawSQL function used throughout the rest of the codebase. Any authenticated user can execute arbitrary SQL statements against all data accessible through the FlightSQL service. Details coordinator/handlers/statisticsv4.go lines 74-107 — V4StatisticsQuery: Contrast with coordinator/handlers/search.go line 194 — secure pattern not followed: query.RawQuery is whatever the caller submitted; it is passed verbatim to the FlightSQL/DuckDB backend. The handler is registered under the protected group (requires JWT), but given that the default JWT secret is empty (see related advisory), this is effectively pre-authentication on a default deployment. PoC Impact SQL Injection / Improper Neutralization of Special Elements (CWE-89). Any authenticated user can execute arbitrary SQL against all data accessible to the FlightSQL/DuckDB backend — including all stored…

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

    Amended from ghsa record GHSA-f46q-3v67-fmm4

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6672

  3. Revision 1 · created ·

    Published from osv record GHSA-f46q-3v67-fmm4

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

Advisory: Homer: Authenticated SQL Injection via Unvalidated rawquery Field in /api/v4/statistics/query
IDs: CVE-2026-62251, GHSA-f46q-3v67-fmm4
Record: https://patchnext.com/advisories/cve-2026-62251 (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: High (CVSS 8.1)
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-20260625085520-a7d027dc684b. A vendor fix does not mean a deployment is fixed.

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

## 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-6672 (OSV record GO-2026-6672 lists affected ranges: Go github.com/sipcapture/homer-app >=0)
- Verified: https://osv.dev/vulnerability/GHSA-f46q-3v67-fmm4 (OSV record GHSA-f46q-3v67-fmm4 lists affected ranges: Go github.com/sipcapture/homer-app >=0 <0.0.0-20260625085520-a7d027dc684b (fixed))
- Verified: https://github.com/advisories/GHSA-f46q-3v67-fmm4 (GitHub-reviewed advisory GHSA-f46q-3v67-fmm4 lists affected ranges: Go github.com/sipcapture/homer-app >=0 <0.0.0-20260625085520-a7d027dc684b)

Commands are suggestions: review each one before running it.

Loading voting…