CVE-2026-41422

The /aggregate/:typename endpoint accepted column and group query parameters that were passed verbatim to goqu.L(), a raw SQL literal expression builder, without any validation. This bypassed all parameterization and allowed authenticated users with any valid session to inject arbitrary SQL expressions.

Root Cause

goqu.L(userInput) in server/resource/resource_aggregate.go inserted user-supplied query parameters directly into the SQL string with no validation.

Fix (v0.11.4)

All goqu.L() calls on user-controlled input were eliminated and replaced with:

• Structural expression parsing supporting all documented API forms
• Schema-based column validation (column names checked against entity schema via TableInfo().GetColumnByName())
• Exact-match allowlist for aggregate functions (count, sum, avg, min, max, first, last) and scalar functions (date, strftime, upper, lower, etc.)
• Safe goqu constructors (goqu.I(), goqu.SUM(), goqu.Func()) for all generated expressions
• allowedTables scope enforcement: qualified column refs (table.col) validated against root entity + explicitly joined tables only

Two additional DoS bugs were fixed in the same commit: uuid.MustParse panic on malformed UUID input and an index-out-of-range panic in ToOrderedExpressionArray on empty sort expressions.

Credits

Reported by @VashuVats.

An authenticated low-privilege user could:

• Extract data from any table via subquery: (SELECT group_concat(email) FROM user_account) as leak
• Disclose database internals: sqlite_version(), (SELECT sql FROM sqlite_master)
• Exfiltrate cross-table data via correlated subqueries

The vulnerability was confirmed locally; user_account.email values were extracted via a crafted column parameter by a non-admin user.

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-41422 has a CVSS score of 8.3 (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.11.4); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-41422? CVE-2026-41422 is a high-severity SQL injection vulnerability in github.com/daptin/daptin (go), affecting versions < 0.11.4. It is fixed in 0.11.4. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
2. How severe is CVE-2026-41422? CVE-2026-41422 has a CVSS score of 8.3 (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.
3. Which versions of github.com/daptin/daptin are affected by CVE-2026-41422? github.com/daptin/daptin (go) versions < 0.11.4 is affected.
4. Is there a fix for CVE-2026-41422? Yes. CVE-2026-41422 is fixed in 0.11.4. Upgrade to this version or later.
5. Is CVE-2026-41422 exploitable, and should I be worried? Whether CVE-2026-41422 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
6. What actually determines whether CVE-2026-41422 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.
7. How do I fix CVE-2026-41422? Upgrade github.com/daptin/daptin to 0.11.4 or later.