# CVE-2026-113461: mk-oracle: Local privilege escalation via insecure Oracle Home library loading


- **Severity:** Medium 5.2 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-2pwc-pprg-4jmv

## What is CVE-2026-113461?

CVE-2026-113461 is a medium-severity vulnerability in Checkmk, published on 21 Oct 2026. 

### Official description

Local privilege escalation in Checkmk 2.5.0p14 allows a local user with write access to the Oracle client library directory of an Oracle home listed in the 'oratab' file or to the 'oratab' file itself to execute code as root if an agent has the 'mk-oracle' plugin enabled.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere), CWE-426 (Untrusted Search Path)

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


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

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

## Is CVE-2026-113461 being exploited?

There is no known exploitation of CVE-2026-113461 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113461 is a medium-severity vulnerability in Checkmk, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-113461 in the wild and no public exploit code.

Affected product: Checkmk. 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-113461/ (Markdown: https://insights.sbomify.com/CVE-2026-113461/index.md)
```

## Sources

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

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