CVE-2026-112181OpenKM Community Edition XML external entity
CVE-2026-112181 is a XML external entity in OpenKM Community Edition, rated high (8.3 on CVSS 4.0).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Received
What it is
The XML parser resolves external entities, so a crafted document can read local files or reach internal hosts.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.
What an attacker gains
A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker read local files or reach internal hosts through the parser. The damage can spread past the vulnerable component into others.
Is it being exploited?
There is no public report of exploitation yet. EPSS estimates a 0.43% chance of exploitation activity in the next 30 days, higher than 37% of scored CVEs.
What to do
- No fixed version is listed yet. Find every place OpenKM Community Edition runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- While there is no fix, review who holds accounts that can reach it.
Description from NVD
Vulnerability due to inadequate restriction of references to external XML entities in OpenKM Community Edition. The XML processing in FormUtils / LocalEntityResolver does not properly restrict the resolution of external resources. An authenticated remote attacker with the ROLE_USER role can exploit the flaw via a REST request. In the 6.3.x branch, this allows the attacker to trigger HTTP requests under their control (SSRF); in 7.0.3, it allows the attacker to read local files and access internal HTTP resources from the server.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- XML and document parsers in APIs and import features. The flaw sits between uploaded or posted documents and the service parsing them.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
- Between uploaded or posted documents and the service parsing them. An attacker who crosses it can read local files or reach internal hosts through the parser.
Questions to answer about your own systems
- Where does OpenKM Community Edition run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.