Daptin: SQL injection via unvalidated goqu.L() calls in aggregate API

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

EPSS

• CVE-2026-41422: 0.34% estimated exploitation activity in the next 30 days; percentile 28.09 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Impact An authenticated low-privilege user could: - Extract data from any table via subquery: (SELECT groupconcat(email) FROM useraccount) as leak - Disclose database internals: sqliteversion(), (SELECT sql FROM sqlitemaster) - Exfiltrate cross-table data via correlated subqueries The vulnerability was confirmed locally; useraccount.email values were extracted via a crafted column parameter by a non-admin user. Root Cause goqu.L(userInput) in server/resource/resourceaggregate.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…

Published by the source

22 Apr 2026, 17:38 UTC

Last modified by the source

8 May 2026, 21:47 UTC

Source last checked

26 Oct 2026, 15:20 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rw2c-8rfq-gwfv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41422

Advisory: Daptin: SQL injection via unvalidated goqu.L() calls in aggregate API
IDs: CVE-2026-41422, GHSA-rw2c-8rfq-gwfv
Record: https://patchnext.com/advisories/cve-2026-41422 (revision 1, source checked 26 Oct 2026, 15:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/daptin/daptin 0.11.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/daptin/daptin: affected < 0.11.4; fixed in 0.11.4

## Suggested inspection (read-only)
- Go github.com/daptin/daptin: 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/daptin/daptin.
- 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://github.com/advisories/GHSA-rw2c-8rfq-gwfv (GitHub-reviewed advisory GHSA-rw2c-8rfq-gwfv lists affected ranges: Go github.com/daptin/daptin >=0 <0.11.4)

Commands are suggestions: review each one before running it.