Vulnerability 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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/llmware-ai/llmware
- https://github.com/llmware-ai/llmware/blob/v0.4.6/llmware/resources.py
- https://github.com/llmware-ai/llmware/issues/1304
- https://www.vulncheck.com/advisories/llmware-0.4.6-sql-injection-via-unescaped-f
FAQ
What is CVE-2026-85689?
CVE-2026-85689 is a vulnerability with a CVSS score of 6.5 (MEDIUM). 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 wit...
How severe is CVE-2026-85689?
CVE-2026-85689 has been rated MEDIUM with a CVSS base score of 6.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-85689?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.