Quick answers
- Is CVE-2026-113461 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-113461 being exploited in the wild.
- How severe is CVE-2026-113461?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- Checkmk 2.5.0p14.
- Is there a fix for CVE-2026-113461?
- Yes: fixed in Checkmk 2.5.0p15. Until then: Enable the permissions_check option set to yes in the mk-oracle configuration YAML to validate file permissions. Additionally, audit and restrict write access to Oracle home library directories and the oratab file to authorized users only. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-113461 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2026-113461?
- Check whether you run Checkmk at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Checkmk 2.5.0p15
Enable the permissions_check option set to yes in the mk-oracle configuration YAML to validate file permissions. Additionally, audit and restrict write access to Oracle home library directories and the oratab file to authorized users only.
Technical details
The mk-oracle plugin in Checkmk 2.5.0p14 loads Oracle home libraries from paths listed in the oratab file without properly validating directory ownership and permissions. An attacker with write access to these libraries or the oratab file itself can replace or modify them to execute arbitrary code when the agent runs with elevated privileges. The fix in 2.5.0p15 validates file ownership and rejects unsafe configurations, controlled by the permissions_check option.
Affected products
- Checkmk Checkmk 2.5.0p14
Timeline
- 2026-10-21: disclosed
- 2026-10-21: patched