Skip to main content
VulnerabilityPublished

CVE-2026-24096: Checkmk · Improper Handling of Insufficient Permissions or Privileges

Affects CheckmkSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.5.0b2 or 2.4.0p25 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.5.0b2, 2.4.0p25
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade Checkmk to 2.5.0b2 or 2.4.0p25.

Affected software

ProductAffectedFixed in
Checkmk GmbHCheckmkAffected
  • >=2.5.0b1 <2.5.0b2
Fixed in
  • 2.5.0b2
Checkmk GmbHCheckmkAffected
  • >=2.4.0 <2.4.0p25
Fixed in
  • 2.4.0p25

AI-suggested

If you cannot patch yet, administrators should restrict access to the REST API Quick Setup endpoints by implementing network-level controls such as firewall rules or API gateway policies limiting access to trusted users and systems only. Additionally, review and tighten user role assignments within Checkmk to minimize the number of users with low-level access that could exploit this vulnerability. Employ monitoring and alerting on unusual API activity or configuration changes to detect potential exploitation attempts early. Conduct regular audits of permissions and API usage logs to identify anomalous behavior. If feasible, isolate Checkmk instances in segmented network zones to reduce exposure. Engage with Checkmk support channels for any available workarounds or interim fixes. Finally, maintain an up-to-date inventory of Checkmk deployments and ensure timely application of security updates to reduce the attack surface.

Description

Insufficient permission validation on multiple REST API Quick Setup endpoints in Checkmk 2.5.0 (beta) before version 2.5.0b2 and 2.4.0 before version 2.4.0p25 allows low-privileged users to perform unauthorized actions or obtain sensitive information

References

Community reviews

Loading reviews…