# CVE-2026-85689: llmware 0.4.6 SQL Injection via unescaped filter values

> Attackers can inject SQL via unescaped filter values in llmware to disclose unauthorized rows from SQLite or PostgreSQL databases.

- **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:** No
- **Published:** 4 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-xw8g-m37q-fhx8

## What is CVE-2026-85689?

CVE-2026-85689 is a high-severity SQL injection vulnerability in llmware-ai llmware, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

llmware 0.4.6 contains an SQL injection vulnerability in the collection-database layer (llmware/resources.py) where filter and lookup values are directly string-interpolated into SQL WHERE clauses without parameterization or escaping, in both the SQLite and PostgreSQL backends. The filter validator only checks keys against an allow-list and never sanitizes values. Attacker-controlled filter values reaching the public API via Library.block_lookup and Query.text_query_with_custom_filter / text_query_by_author_or_speaker can neutralize the intended filter to disclose rows the caller was scoped out of (cross-document/cross-collection disclosure); on PostgreSQL the flaw permits boolean- and UNION-based SQL injection.

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

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


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

No fix has been published for CVE-2026-85689 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85689 being exploited?

There is no known exploitation of CVE-2026-85689 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85689 is a high-severity SQL injection vulnerability in llmware-ai llmware, published on 4 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85689 in the wild and no public exploit code.

Affected product: llmware-ai llmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-85689/ (Markdown: https://insights.sbomify.com/CVE-2026-85689/index.md)
```

## Sources

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

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