Privilege escalation via unprotected Windows agent data folder
- Exploited
- No known exploitation
- Fix
- Fixed in 2.5.0p18, 2.4.0p39, 2.3.0p52
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.5.0p18, 2.4.0p39, 2.3.0p52.
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 6/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Checkmk Windows agent contains a flaw in how it sets permissions on its data folder, letting a local user with ordinary login access run arbitrary code as SYSTEM and read the agent controller's private key. The attacker reaches it locally by placing scripts in the agent's plugins or local folders.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Incorrect permissions on the Checkmk Windows agent's data directory, caused by a race condition that discards the permission changes during service start, in Checkmk <2.5.0p18, <2.4.0p39, <2.3.0p52 and 2.2.0 (EOL) allow a local user to execute arbitrary code as SYSTEM by placing scripts in the agent's plugins or local folders, and to read the agent controller's private key.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 61 if added to CISA KEV
- Would score about 56 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.5.0p18, 2.4.0p39, 2.3.0p52.
Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
- Checkmk GmbH Checkmk
From 2.5.0 · fixed in 2.5.0p18; From 2.4.0 · fixed in 2.4.0p39; From 2.3.0 · fixed in 2.3.0p52
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-111573
Is CVE-2026-111573 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-111573?
Checkmk: from 2.5.0 before 2.5.0p18; from 2.4.0 before 2.4.0p39; from 2.3.0 before 2.3.0p52.Source: cve.now feed data
How do I fix CVE-2026-111573?
Upgrade to a fixed version: 2.5.0p18, 2.4.0p39, 2.3.0p52.Source: cve.now feed data