# CVE-2026-44349: Daptin fuzzy search injects unvalidated column name into raw SQL

> An authenticated user can exploit unvalidated column names in fuzzy search to perform SQL injection and read the entire database.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 May 2026
- **Updated:** 8 May 2026
- **Also known as:** GHSA-pwqg-q8pg-pp6r, GO-2026-5555

## What is CVE-2026-44349?

CVE-2026-44349 is a high-severity SQL injection vulnerability in daptin, published on 7 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Daptin is a GraphQL/JSON-API headless CMS. Prior to version 0.11.5, processFuzzySearch in server/resource/resource_findallpaginated.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 fuzzy_any, fuzzy_all). Any authenticated user — including one who self-registered with no admin involvement — can read the entire database. This issue has been patched in version 0.11.5.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-44349?

3 open source packages ship an affected version, including github.com/daptin/daptin.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/daptin/daptin` | Go | All versions | 0.11.5 |
| `github.com/daptin/daptin` | Go | All versions | 0.11.5 |
| `github.com/daptin/daptin` | Go | All versions | 0.11.5 |

## How do I fix CVE-2026-44349?

Upgrade github.com/daptin/daptin to 0.11.5 or later.

## Is CVE-2026-44349 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44349 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44349 and fix it if it is affected.

What it is: CVE-2026-44349 is a high-severity SQL injection vulnerability in daptin, published on 7 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44349 exists.

Affected packages and fixed versions:
- github.com/daptin/daptin (Go): affected all versions; fixed in 0.11.5
- github.com/daptin/daptin (Go): affected all versions; fixed in 0.11.5
- github.com/daptin/daptin (Go): affected all versions; fixed in 0.11.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44349/ (Markdown: https://insights.sbomify.com/CVE-2026-44349/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44349
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44349
- OSV: https://osv.dev/vulnerability/CVE-2026-44349

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44349/
Summaries are generated and may contain mistakes; the official description above is the record.