# CVE-2026-109170: LogicalDOC Community Edition through 9.3 HQL Injection via documents.xml indexed Parameter

> Authenticated attackers can inject HQL queries to bypass folder permissions and extract restricted document metadata and database contents.

- **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:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-q5m2-qppc-8h4c

## What is CVE-2026-109170?

CVE-2026-109170 is a high-severity SQL injection vulnerability in LogicalDOC Community Edition, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

LogicalDOC Community Edition through 9.3 contains an HQL injection vulnerability in DocumentsDataServlet that allows authenticated users to manipulate queries via the unvalidated indexed parameter. Attackers with read access to any folder can inject boolean HQL expressions to bypass folder scope and read-permission checks, listing restricted document metadata and extracting database contents.

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

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


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

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

## Is CVE-2026-109170 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109170 is a high-severity SQL injection vulnerability in LogicalDOC Community Edition, published on 12 Oct 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-109170 in the wild and no public exploit code.

Affected product: LogicalDOC Community Edition. 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-109170/ (Markdown: https://insights.sbomify.com/CVE-2026-109170/index.md)
```

## Sources

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

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