CVE
OpenKM Community Edition XXE file read and SSRF in REST XML parser
Affects OpenKM Community Edition 6.3.3 through 6.3.13 and 7.0.3 in the FormUtils and LocalEntityResolver components. Fixed in 7.0.4.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 7.0.4
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected: OpenKM Community Edition 6.3.3 through 6.3.13 and 7.0.3, in the FormUtils / LocalEntityResolver components.
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.43% · 37th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OpenKM Community Edition contains an XML entity processing flaw that lets a remote attacker who has a basic user login (ROLE_USER) send a crafted REST request. Depending on the branch, the attacker can make the server send requests they control (SSRF) or read local files and reach internal HTTP resources.
Read the original description
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.
Who should check
Teams running OpenKM Community Edition 6.3.3 to 6.3.13 or 7.0.3, including the FormUtils / LocalEntityResolver components
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected: OpenKM Community Edition 6.3.3 through 6.3.13 and 7.0.3, in the FormUtils / LocalEntityResolver components.Upgrade to a fixed version: 7.0.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-112181 (Multiple Vulnerabilities in OpenKM Community Edition), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-112181 (entry last updated 2026-11-13):
Affected:
- OpenKM OpenKM Community Edition: from 6.3.3, through 6.3.13
Fixed versions: 7.0.4.
Conditions (all must be true for the bug to be hit):
- Affected: OpenKM Community Edition 6.3.3 through 6.3.13 and 7.0.3, in the FormUtils / LocalEntityResolver components. (source: https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-openkm-community-edition)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-112181 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-112181 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-openkm-community-edition
- https://www.cve.org/CVERecord?id=CVE-2026-112181
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-112181
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-112181"}.Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- OpenKM OpenKM Community Edition
From 6.3.3 · through 6.3.13
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-112181
Is CVE-2026-112181 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The flaws let an attacker read local files and reach internal HTTP resources on the server in 7.0.3. In the 6.3.x versions, they let an attacker trigger attacker-controlled HTTP requests, which is SSRF.Source: incibe.es, cve.org
Which versions are affected by CVE-2026-112181?
OpenKM Community Edition: from 6.3.3 through 6.3.13.Source: cve.now feed data