Checkmk path traversal in host label sync allows code execution
Affects Checkmk 2.4.0 and 2.5.0 setups with remote sites that are potentially untrusted. The vendor's rating is not given here, and CVSS scores it 9.4 (critical). Fixed in 2.4.0p40 and 2.5.0p19.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.5.0p19, 2.4.0p40
- Who is exposed
- Specific setups only
Summary
Checkmk is affected by a path traversal flaw in its discovered host label synchronization. An attacker who controls a remote site in a distributed monitoring setup can reach it over the network with low-privilege login and no user action, write arbitrary files on the central site, and execute code as the central site user.
Written by a model
Original description
Path traversal in the discovered host label synchronization in Checkmk <2.5.0p19, <2.4.0p40 and 2.3.0 (EOL) allows an attacker in control of a remote site in a distributed monitoring setup to write arbitrary files on the central site and thereby execute code as the central site user.
Who should check
Anyone running Checkmk distributed monitoring with potentially untrusted remote sites; affected versions 2.5.0, 2.4.0 and 2.3.0 (EOL).
“Every setup with potentially untrusted remote sites is affected.”
What to do
Check whether your setup matches what the bug needs.
Distributed monitoring setup with remote sites that are potentially untrustedUpgrade to a fixed version: 2.5.0p19, 2.4.0p40.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-118965 (Path traversal in host label synchronization allows code execution on the central site from a remote site), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-118965 (entry last updated 2026-11-16):
Affected:
- Checkmk GmbH Checkmk: from 2.5.0, fixed in 2.5.0p19; from 2.4.0, fixed in 2.4.0p40
Fixed versions: 2.5.0p19, 2.4.0p40.
Conditions (all must be true for the bug to be hit):
- Distributed monitoring setup with remote sites that are potentially untrusted (source: https://checkmk.com/werk/22120)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-118965 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-118965 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://checkmk.com/werk/22120
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-118965
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-118965"}.Affected versions
- Checkmk GmbH CheckmkFrom 2.5.0 · fixed in 2.5.0p19; From 2.4.0 · fixed in 2.4.0p40
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.4, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now3 days
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
2 days - Record last updated
Public exploit activity
- EPSS: 0.46%
- Posted on X by cve.now Nov 11
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | checkmk.com · werk/22120 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-118965 |
| Record | NVD · CVE-2026-118965 |
Questions about CVE-2026-118965
Is CVE-2026-118965 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
What does this mean?
A path traversal flaw in host label synchronization lets a malicious remote site write arbitrary files on the central site. That can lead to code execution as the central site user.
Source: checkmk.com
Which versions are affected by CVE-2026-118965?
Checkmk: from 2.5.0 before 2.5.0p19; from 2.4.0 before 2.4.0p40.
Source: cve.now feed data
Am I affected, and how do I check?
Checkmk 2.4.0 before 2.4.0p40 and 2.5.0 before 2.5.0p19 are affected. The issue applies to distributed monitoring setups with remote sites that are potentially untrusted. Check the Checkmk version on the central site and whether it runs remote sites.
Source: checkmk.com
How do I fix CVE-2026-118965?
Update to 2.4.0p40 for the 2.4.0 branch or to 2.5.0p19 for the 2.5.0 branch.
Source: checkmk.com
Related
- CVE-2026-120495Arbitrary file write and code execution via crafted Synthetic Monitoring agent data
- CVE-2026-121374Arbitrary file write and code execution via excluded node roles in Kubernetes special agent
- CVE-2026-14452Open redirect and XSS via reset_url parameter
- CVE-2026-117611Trust of compromised eMudhra root CA in bundled CA stores
- CVE-2026-15576Agent receiver accepts mTLS requests without a client certificate
- CVE-2026-111573Privilege escalation via unprotected Windows agent data folder
No corrections so far. Something wrong on this page? Report an error.