# CVE-2026-14852: mk_sap_hana: Privilege escalation via crafted sapstartsrv process name

> A local unprivileged user can execute arbitrary commands as root by spoofing a SAP HANA process name in Checkmk's agent plugin.

- **Severity:** Medium 5.2 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-92pj-jr25-ww3p, UBUNTU-CVE-2026-14852

## What is CVE-2026-14852?

CVE-2026-14852 is a medium-severity command injection vulnerability in Checkmk, published on 14 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Privilege escalation in Checkmk versions 2.5.0 before 2.5.0p9, 2.4.0 before 2.4.0p34, 2.3.0 before 2.3.0p49, and 2.2.0 (EOL) allows a local unprivileged user to execute arbitrary commands as root by starting a process crafted to look like a SAP HANA instance. Without an explicit database configuration, the mk_sap_hana agent plugin derives instance identifiers from the process list and uses them to build a command executed with elevated privileges (requires the plugin to run as root with RUNAS=agent).

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-14852 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14852 is a medium-severity command injection vulnerability in Checkmk, published on 14 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14852 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-14852/ (Markdown: https://insights.sbomify.com/CVE-2026-14852/index.md)
```

## Sources

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

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