CVE
OpenKM Community Edition remote code execution in workflow REST endpoints
Only affects OpenKM Community Edition 6.3.12 and 6.3.13 with workflow definition management (jBPM engine); the 7.x branch is not affected. Fixed in 6.3.14.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6.3.14
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. OpenKM CE 6.3.12 or 6.3.13 with workflow definition management (jBPM engine). The OpenKM CE 7.x branch is not affected.
- 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
- 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? →
- 17/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
Attackers who have a basic user account on OpenKM Community Edition can reach this flaw over the network, because the REST endpoints that register and run workflow process definitions do not check the user's role. A successful attacker can run Java code and operating system commands with the service's privileges, which in the official Docker image means root.
Read the original description
Unauthorization vulnerability in the management of workflow definitions in OpenKM Community Edition. The REST endpoints registerProcessDefinition and runProcessDefinition require authentication but do not verify roles in the WorkflowService or in lower layers. An attacker with the ROLE_USER role can register and execute a process definition containing BeanShell scripts, allowing them to execute Java code and operating system commands with the service’s privileges. In the official Docker image, the process runs as root.
Who should check
Teams running OpenKM Community Edition 6.3.12 or 6.3.13 with workflow definition management (jBPM engine); the 7.x branch is not affected.
Read the source excerpt
“OpenKM Community Edition, versions 6.3.12 and 6.3.13; workflow definition management.”
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.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
OpenKM CE 6.3.12 or 6.3.13 with workflow definition management (jBPM engine). The OpenKM CE 7.x branch is not affected.Upgrade to a fixed version: 6.3.14.
Workaround: Block non-administrator access to /OpenKM/services/rest/workflow/* and /OpenKM/services/OKMWorkflow on the reverse proxy or firewall.
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-112182 (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-112182 (entry last updated 2026-11-13):
Affected:
- OpenKM OpenKM Community Edition: versions 6.3.12, 6.3.13
Fixed versions: 6.3.14.
Conditions (all must be true for the bug to be hit):
- OpenKM CE 6.3.12 or 6.3.13 with workflow definition management (jBPM engine). (source: https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-openkm-community-edition)
- The OpenKM CE 7.x branch is not affected. (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.
Workaround: Block non-administrator access to /OpenKM/services/rest/workflow/* and /OpenKM/services/OKMWorkflow on the reverse proxy or firewall. (source: https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-openkm-community-edition)
CISA KEV: CVE-2026-112182 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-112182 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
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-112182
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-112182"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- OpenKM OpenKM Community Edition
6.3.12, 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-112182
Is CVE-2026-112182 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?
An attacker can execute Java code and operating system commands with the service's privileges. In the official Docker image, the process runs as root.Source: incibe.es
Which versions are affected by CVE-2026-112182?
OpenKM Community Edition: versions 6.3.12, 6.3.13.Source: cve.now feed data
Am I affected, and how do I check?
OpenKM Community Edition 6.3.12 and 6.3.13 with workflow definition management (jBPM engine). The 7.x branch does not include the jBPM engine and is not affected.Source: incibe.es
How do I fix CVE-2026-112182?
Update to OpenKM CE 6.3.14 when it becomes available. Until then, block non-administrator access to /OpenKM/services/rest/workflow/* and /OpenKM/services/OKMWorkflow on the reverse proxy or firewall.Source: incibe.es