Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Checkmk Remote Site Code Execution (CVE-2026-118965)

CVE-2026-118965 is a Checkmk path traversal flaw in discovered host label synchronization.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-118965
Vendor
Checkmk
Affected Product
Checkmk
Exploitation
Not confirmed
Published
2026-11-11

A person controlling a remote site in distributed monitoring can make the central site write arbitrary files.Checkmk says this can lead to code execution on the central site. The NVD description specifies execution as the central site user, and Checkmk rates the issue CVSS 4.0 9.4 Critical.

What it allows

How Does CVE-2026-118965 Work?

The central Checkmk site queries remote sites for discovered host labels and writes the responses to disk. Checkmk says the target filename was not sanitized before that write.

A malicious remote site can exploit that filename handling to make the central site write arbitrary files. The NVD description says this can lead to code execution as the central site user.

The attacker must control a remote site in a distributed monitoring setup. This is a trust boundary failure between a remote site and its central site, rather than an unauthenticated attack on any Checkmk installation.

What Is Known About Exploitation?

The cited Checkmk and NVD records describe the flaw and its impact, but do not establish exploitation in the wild. CISA KEV catalog version 2026.11.10 did not list CVE-2026-118965.

Brandefense Blackhole counted two Telegram posts about the CVE from August 13 to November 11, 2026. These discussion posts signal attention to the flaw; their count does not establish successful exploitation.

Who is affected

Which Checkmk Sites Are Affected?

Checkmk says setups with potentially untrusted remote sites are affected. NVD identifies versions before 2.5.0p19, versions before 2.4.0p40, and the end-of-life 2.3.0 branch.

Checkmk lists the 2.5.0p19 and 2.4.0p40 security fixes for Community, Pro, Ultimate, Cloud, and Ultimate MT editions. The advisory also lists 3.0.0b1 as not yet released; it does not identify a supported 2.3.0 fix.

Checkmk fix levels
2.5 branch.
Update to 2.5.0p19 or later.
2.4 branch.
Update to 2.4.0p40 or later.
2.3 branch.
End of life; plan migration.

What Should Defenders Do?

Prioritize central sites connected to remote sites that another party could control. Inventory those trust relationships using a vulnerability management process, then verify each site's installed Checkmk version.

Update supported 2.5 and 2.4 deployments to the fixed patch levels. Migrate end-of-life 2.3 deployments to a supported release, and use vulnerability prioritization to schedule central sites with untrusted remote connections first.

As a Brandefense precaution, review central site file changes and execution activity after remote label synchronization. Investigate unexpected changes and restrict distributed monitoring relationships to remote sites the organization trusts.

For a broader explanation of the underlying process, see the vulnerability management glossary. Checkmk says the fix validates target filenames, so confirm the updated release is installed before relying on monitoring alone.

Timeline

  1. 2026-10-29

    Checkmk dated Werk #22120, describing the security fix for discovered host label synchronization.

  2. 2026-11-11

    NVD published the CVE-2026-118965 record with Checkmk's CVSS 4.0 score.

What to do

  1. Map remote site trust

    Identify central Checkmk sites connected to remote sites that another party may control. Prioritize these distributed monitoring relationships for review.

  2. Install fixed Checkmk releases

    Update the 2.5 branch to 2.5.0p19 or later and the 2.4 branch to 2.4.0p40 or later. Verify the installed version after deployment.

  3. Migrate Checkmk 2.3

    Plan migration from the end-of-life 2.3 branch to a supported release. The cited Checkmk advisory does not identify a 2.3 fix.

  4. Review central site activity

    As a Brandefense precaution, investigate unexpected central site file changes or execution activity after remote label synchronization.

What Brandefense can do

Frequently Asked Questions

What is CVE-2026-118965?

It is a Checkmk path traversal flaw in discovered host label synchronization. Control of a remote site can lead to arbitrary file writes and code execution on the central site.

Does CVE-2026-118965 affect standalone Checkmk sites?

The cited attack requires control of a remote site in a distributed monitoring setup. Checkmk identifies setups with potentially untrusted remote sites as affected.

Which Checkmk versions fix CVE-2026-118965?

Checkmk lists 2.5.0p19 and 2.4.0p40 as fixed releases. The 2.3.0 branch is end of life, with no supported fix identified in the cited advisory.

Is CVE-2026-118965 listed in CISA KEV?

CISA KEV catalog version 2026.11.10 did not list this CVE. That catalog status does not prove that exploitation has or has not occurred.

What is the impact of a compromised Checkmk remote site?

Checkmk says it can cause arbitrary file writes on the central site. NVD states that the resulting code executes as the central site user.

Sources

  1. Werk #22120: Code execution through compromised remote siteCheckmk
  2. CVE-2026-118965 DetailNational Vulnerability Database
  3. Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →