Daptin fuzzy search injects unvalidated column name into raw SQL

Exploitation

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

CVSS 4.0

7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-44349: 0.30% estimated exploitation activity in the next 30 days; percentile 23.31 (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 processFuzzySearch in server/resource/resourcefindallpaginated.go:1484 splits the user-supplied column parameter by comma and interpolates each segment directly into goqu.L(fmt.Sprintf("LOWER(%s) LIKE ?", prefix+col)) raw SQL with no column whitelist check. The entry point is GET /api/<entity with operator=fuzzy (or fuzzyany, fuzzyall). Any authenticated user — including one who self-registered with no admin involvement — can read the entire database. --- Details At resourcefindallpaginated.go:1761, when the operator is fuzzy, fuzzyany, or fuzzyall, execution routes to processFuzzySearch (line 1763) before processQueryFilter (line 1780). processQueryFilter is the only path that calls GetColumnByName (line 1351), which validates column names against the table schema. The fuzzy branch never reaches that check. Inside processFuzzySearch (line 1484), filterQuery.ColumnName is split by comma. After strings.TrimSpace (line 1486), each segment is routed to a DB-driver-specific…

Published by the source

6 May 2026, 22:10 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-pwqg-q8pg-pp6r

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

# Patch Next advisory brief: CVE-2026-44349

Advisory: Daptin fuzzy search injects unvalidated column name into raw SQL
IDs: CVE-2026-44349, GHSA-pwqg-q8pg-pp6r
Record: https://patchnext.com/advisories/cve-2026-44349 (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 7.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/daptin/daptin 0.11.5. 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.5

## 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-pwqg-q8pg-pp6r (GitHub-reviewed advisory GHSA-pwqg-q8pg-pp6r lists affected ranges: Go github.com/daptin/daptin >=0 <=0.11.4)

Commands are suggestions: review each one before running it.