CVE-2026-41422: GO-2026-5640 - Daptin: SQL injection via unvalidated goqu.L() calls in aggregate API in github.com/daptin/daptin

CVE-2026-41422 · Severity: low · CVSS 3.1 · Published 2026-06-25

Daptin: SQL injection via unvalidated goqu.L() calls in aggregate API in github.com/daptin/daptin

Technologies: github.com/daptin/daptin (Go). Vendors: Go.

Quick answers

Is CVE-2026-41422 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-41422 being exploited in the wild.
How severe is CVE-2026-41422?
Low severity, with a CVSS score of 3.1, published 25 June 2026.
Which products and versions are affected?
github.com/daptin/daptin (Go) SEMVER:introduced=0,fixed=0.11.4.
Is there a fix for CVE-2026-41422?
Yes. github.com/daptin/daptin (Go): upgrade to 0.11.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-41422?
Check whether you run github.com/daptin/daptin (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/daptin/daptin (Go): upgrade to 0.11.4 or later
    go get github.com/daptin/daptin@v0.11.4

Affected products

  • github.com/daptin/daptin (Go) SEMVER:introduced=0,fixed=0.11.4

Identifiers

  • CVE-2026-41422
  • GHSA-rw2c-8rfq-gwfv
  • GO-2026-5640

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.