dbcve.org
CheckmkApplication

CVE-2024-47091

HIGH · 7.8 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Privilege escalation in the mk_mysql agent plugin on Windows in Checkmk <2.4.0p29, <2.3.0p47, and 2.2.0 (EOL) allows a local unprivileged user able to create a Windows service whose name matches 'MySQL' or 'MariaDB' (or with write access to a binary referenced by such a service) to execute arbitrary code in the context of the Checkmk agent service, which typically runs as SYSTEM.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The mk_mysql agent plugin in Checkmk for Windows searches for and interacts with Windows services named 'MySQL' or 'MariaDB'. A local unprivileged attacker can create a malicious service with one of these names (or gain write access to a referenced binary) to achieve code execution as SYSTEM when the Checkmk agent service processes the service, typically running with elevated privileges.

MitigationUpgrade Checkmk to version 2.4.0p29, 2.3.0p47, or later; alternatively, disable or restrict the mk_mysql plugin if MySQL monitoring is not required, and limit service creation permissions to prevent unprivileged users from creating services with these names.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CheckmkApplication
Affected:= 2.2.0= 2.3.0= 2.4.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Checkmk version on Windows
    Open a command prompt and run: 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Check_MK" /v DisplayVersion' or check the Add/Remove Programs list for Checkmk version
    Affected if Version matches 2.2.0, 2.3.0, or 2.4.0 (any patch level)
  2. Locate the mk_mysql plugin
    Check if the file 'mk_mysql.ps1' or 'mk_mysql.exe' exists in the Checkmk agent plugins directory, typically at 'C:\Program Files (x86)\check_mk\agents\plugins\' or within the agent installation folder
    Affected if The mk_mysql plugin file is present in the Checkmk agent plugins directory
  3. Verify if mk_mysql plugin is enabled
    Check the Checkmk agent configuration or scheduled task for the mk_mysql plugin. Look in the agent configuration file (usually at 'C:\ProgramData\check_mk\agent\config\mk_mysql.cfg' or review the Windows scheduled task that runs the agent plugins)
    Affected if The plugin is configured to run as part of the Checkmk agent scheduled task or service
  4. Check for MySQL or MariaDB Windows services
    Run 'sc query type= service state= all' in command prompt and search for services named 'MySQL' or 'MariaDB', or use 'Get-Service | Where-Object {$_.Name -like "*MySQL*" -or $_.Name -like "*MariaDB*"}' in PowerShell
    Affected if A Windows service with the exact name 'MySQL' or 'MariaDB' exists on the system
  5. Check service creation permissions
    Run 'sc sdset MySQL' or 'sc sdset MariaDB' (if either service exists) to view the security descriptor, or use PowerShell with Get-Acl on HKLM:\SYSTEM\CurrentControlSet\Services\ to review who can create service objects
    Affected if Non-privileged users have permission to create new services (verified via security descriptor or registry ACL)
  6. Confirm Checkmk agent runs with elevated privileges
    Check the Checkmk agent Windows service or scheduled task properties to verify it runs under the SYSTEM account or another privileged account
    Affected if The Checkmk agent service or scheduled task runs as SYSTEM or a user with administrative privileges

If Checkmk version 2.2.0, 2.3.0, or 2.4.0 is installed on Windows with the mk_mysql plugin enabled, and a MySQL/MariaDB service exists (or unprivileged users can create one), the environment is vulnerable to local privilege escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Checkmk to version 2.4.0p29, 2.3.0p47, or later; alternatively, disable or restrict the mk_mysql plugin if MySQL monitoring is not required, and limit service creation permissions to prevent unprivileged users from creating services with these names.

Recommended fix High confidence

2.4.0p29 or later, or 2.3.0p47 or later (2.2.0 is EOL with no patch)

  1. Identify the current Checkmk version by checking the agent or web interface
  2. If running 2.4.0.x, upgrade to version 2.4.0p29 or later
  3. If running 2.3.0.x, upgrade to version 2.3.0p47 or later
  4. If running 2.2.0, note that this version is End of Life (EOL) with no patch available; plan migration to a supported version (2.3.0p47+ or 2.4.0p29+)
  5. After upgrade, verify the mk_mysql agent plugin has been updated and the vulnerability is resolved
  6. Restart the Checkmk agent service to ensure the updated plugin is loaded
Caveat No breaking changes documented for these patch releases; standard version upgrade procedures apply

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Checkmk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47091 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47091 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data