{
  "id": "CVE-2026-85689",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-85689",
  "published_at": "2026-09-04T14:32:33.799Z",
  "title": "llmware 0.4.6 SQL Injection via unescaped filter values",
  "vendor": "llmware-ai",
  "product": "llmware",
  "cvss": {
    "score": 7.1,
    "source": "cna",
    "vector": "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"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.",
  "cwe": "CWE-89",
  "cvss_by_source": {
    "cna": 7.1
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "llmware-ai",
        "product": "llmware",
        "ranges": [
          "\u003c= 0.4.6"
        ],
        "fixed_in": null
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
