Summary
Homer: Authenticated SQL Injection via Unvalidated rawquery Field in /api/v4/statistics/query
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/statistics_v4.go lines 74-107, V4StatisticsQuery:
query := &model.V4StatisticsQuery{}
if err = c.Bind(query); err != nil { ... }
// No ValidateRawSQL call here, contrast with other handlers:
results, err := h.flightService.Query(c.Request().Context(), query.RawQuery)
Contrast with coordinator/handlers/search.go line 194, secure pattern not followed:
if err := sqlvalidator.ValidateRawSQL(rawQuery); err != nil {
return c.JSON(http.StatusBadRequest, ...)
}
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
# With a valid JWT (or empty JWT secret bypass):
curl -s -X POST http://<homer-host>/api/v4/statistics/query \
-H "Authorization: Bearer <jwt>" \
-H "Content-Type: application/json" \
-d '{
"param": {
"query": [{"rawquery": "SELECT * FROM information_schema.tables"}]
}
}'
# Returns all table names accessible to the DuckDB FlightSQL service
# Exfiltrate all stored call records:
# "rawquery": "SELECT * FROM hep LIMIT 1000"
# Arbitrary DuckDB SQL is accepted including INSTALL/LOAD for extension-based exfiltration
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 VoIP call records, SIP messages, and metadata. Combined with the authentication bypass when JWT secret is empty, this is exploitable without credentials.
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
CVE-2026-62251 has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.0.0-20260625085520-a7d027dc684b); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Apply sqlvalidator.ValidateRawSQL() to query.RawQuery before passing it to h.flightService.Query(), matching the pattern already used in search.go and transactions_v4.go.
If possible, please apply for a CVE number when posting.
Frequently Asked Questions
- What is CVE-2026-62251? CVE-2026-62251 is a high-severity SQL injection vulnerability in github.com/sipcapture/homer-app (go), affecting versions < 0.0.0-20260625085520-a7d027dc684b. It is fixed in 0.0.0-20260625085520-a7d027dc684b. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- How severe is CVE-2026-62251? CVE-2026-62251 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/sipcapture/homer-app are affected by CVE-2026-62251? github.com/sipcapture/homer-app (go) versions < 0.0.0-20260625085520-a7d027dc684b is affected.
- Is there a fix for CVE-2026-62251? Yes. CVE-2026-62251 is fixed in 0.0.0-20260625085520-a7d027dc684b. Upgrade to this version or later.
- Is CVE-2026-62251 exploitable, and should I be worried? Whether CVE-2026-62251 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-62251 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-62251? Upgrade
github.com/sipcapture/homer-appto 0.0.0-20260625085520-a7d027dc684b or later.