Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.

Atlassian cookies and tracking notice, (opens new window)

Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)

Checkmk Knowledge Base

Checkmk Knowledge Base

Checkmk Knowledge Base

Results will update as you type.

Accessibility statement for Checkmk
Agent Bakery
Appliance
BI - Business Intelligence
Checkmk Micro Core (CMC)
Checks & Agents
Distributed monitoring
Event Console
Grafana
Graphical User Interface (GUI)
How-to articles
Licensing & Customer Portal
Management boards
Nagvis
Notifications
Round Robin Database (RRD)
Security
- Considerations before running the agent as an unprivileged user
- CVE
Troubleshooting articles
Why Checkmk uses memory_working_set for K8s container monitoring
Windows

You‘re viewing this with anonymous access, so some content might be blocked.

/

CVE

Updated Oct 15, 2025

CVE

This page lists CVE-related articles.

Checkmk is not affected by Dirty Pipe Exploit (CVE-2022-0847)
Checkmk is not affected by Log4j (CVE-2021-44228)
Checkmk is not affected by RediShell (CVE-2025-49844)
Checkmk is not affected by Spring4Shell (CVE-2022-22965)

Related articles

{"serverDuration": 26, "requestCorrelationId": "e1f7b30403714f4293e70653fc28816f"}