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.
CVE-2026-109170
MEDIUMPre-NVD 6.56.5Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-12. A secondary CVSS source baseline 6.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5MEDIUMhigh confidence
- EG Risk
- 29EG Risk 29/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity65% × 45%The EG Score, 6.5 of 10.Exploitation0.3% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release. - EPSS PROB
- 0.3%
- EPSS %ILE
- 18th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 12, 2026
Last Modified
October 13, 2026
Advisory Details (5)
Auto-updated Oct 12, 2026Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page
LogicalDOC Community Edition through 9.3 HQL Injection via documents.xml indexed Parameter | Advisories | VulnCheck
https://www.vulncheck.com/advisories/logicaldoc-community-edition-through-9.3-hql-injection-via-documents-xml-indexed-parameterWeb page
GitHub - logicaldoc/community: LogicalDOC Community open source document management system https://www.logicaldoc.com · GitHub
https://github.com/logicaldoc/communityWeb page
community/logicaldoc-webapp/src/main/java/com/logicaldoc/web/data/DocumentsDataServlet.java at 9.3 · logicaldoc/community · GitHub
https://github.com/logicaldoc/community/blob/9.3/logicaldoc-webapp/src/main/java/com/logicaldoc/web/data/DocumentsDataServlet.java#L443GitHub commit
commit c3bbfd4641f1 (logicaldoc/community)
Fix landed in logicaldoc/community commit c3bbfd4641f1 — awaiting tagged release
https://github.com/logicaldoc/community/commit/c3bbfd4641f1cd2b340f114ea198d3f65b6581eeWeb page
Multiple High-Severity Issues in Community <=9.3.1 (SQLi, Auth Bypass, IDORs, SSRF, RCE patterns) · logicaldoc community · Discussion #119 · GitHub
https://github.com/logicaldoc/community/discussions/119Vendor Advisories for CVE-2026-109170(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-13 21:08 UTCGHSA enrichmentGHSA-q5m2-qppc-8h4c · GitHub severity HIGH · GitHub CVSS 6.5
- 2026-10-13 20:03 UTCEG score recompute
- 2026-10-13 20:03 UTCGHSA enrichmentGHSA-q5m2-qppc-8h4c · GitHub severity HIGH · GitHub CVSS 6.5
- 2026-10-13 18:53 UTCEG score recompute
- 2026-10-13 18:52 UTCGHSA enrichmentGHSA-q5m2-qppc-8h4c · GitHub severity HIGH · GitHub CVSS 6.5
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-12 16:38 UTCEG score recompute
- 2026-10-12 14:26 UTCEG score recompute
- 2026-10-12 13:55 UTCEG score recomputeFirst assessed: 6.5 MEDIUM
- 2026-10-12 13:51 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-109170?
CVE-2026-109170 is a medium-severity vulnerability; its CVE record was published on October 12, 2026. 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…
When was CVE-2026-109170 made public?
CVE-2026-109170 was made public on October 11, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 12, 2026. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
Is CVE-2026-109170 actively exploited?
CVE-2026-109170 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-109170?
CVE-2026-109170 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-109170?
An upstream fix for CVE-2026-109170 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-109170 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-109170
Is Your Infrastructure Affected by CVE-2026-109170?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.