# CVE-2026-42785: OpenKM 6.3.12 Remote Code Execution via Administrative Scripting

> Authenticated administrators can execute arbitrary code via the scripting endpoint, leading to remote code execution on the server.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-w8q9-g33h-9x9m

## What is CVE-2026-42785?

CVE-2026-42785 is a high-severity code injection vulnerability in OpenKM Community Edition, published on 26 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

OpenKM 6.3.12 contains a remote code execution vulnerability that allows authenticated administrators to execute arbitrary Java/BeanShell code through the /admin/Scripting endpoint. Attackers can submit malicious script content with an action=Evaluate parameter to execute operating system commands in the context of the OpenKM application server.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


## How do I fix CVE-2026-42785?

No fix has been published for CVE-2026-42785 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-42785 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42785 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42785 and fix it if it is affected.

What it is: CVE-2026-42785 is a high-severity code injection vulnerability in OpenKM Community Edition, published on 26 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42785 exists.

Affected product: OpenKM Community Edition. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42785/ (Markdown: https://insights.sbomify.com/CVE-2026-42785/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42785
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42785
- OSV: https://osv.dev/vulnerability/CVE-2026-42785

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42785/
Summaries are generated and may contain mistakes; the official description above is the record.