dbcve.org
CheckmkApplication

CVE-2026-24096

HIGH · 8.8 CVSS v3.1 Published 2026-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Insufficient permission validation on multiple REST API Quick Setup endpoints in Checkmk allows low-privileged users to bypass authorization checks and perform unauthorized administrative actions or access sensitive information they should not have access to.

MitigationUpdate Checkmk to version 2.5.0b2 or later for 2.5.x, or version 2.4.0p25 or later for 2.4.x to patch the authorization bypass in REST API Quick Setup endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CheckmkApplication
Affected:= 2.4.0= 2.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Checkmk version
    Use the Checkmk web interface (About page) or run 'cmk --version' command to determine the exact version number
    Affected if Version is 2.4.0 or 2.5.0 (or falls within these major version families before the patches)
  2. Verify REST API is enabled
    Check the Checkmk configuration for REST API settings, typically found in the 'Setup > General > API' web interface section or by reviewing the site configuration
    Affected if REST API access is enabled and accessible to low-privileged users
  3. Review REST API user permissions
    Examine the roles and permissions assigned to REST API users through 'Setup > Users > Roles' or the API token configuration
    Affected if Low-privileged (non-admin) users have REST API access tokens
  4. Inspect Quick Setup endpoint accessibility
    Attempt to access or enumerate Quick Setup REST API endpoints using a low-privileged user's API token (if available) or review API documentation/endpoint configuration
    Affected if Quick Setup endpoints respond to requests from low-privileged accounts without proper authorization rejection

A user is affected if they run Checkmk version 2.4.0 or 2.5.0 with REST API enabled, where low-privileged users can access Quick Setup endpoints without proper authorization enforcement.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Checkmk to version 2.5.0b2 or later for 2.5.x, or version 2.4.0p25 or later for 2.4.x to patch the authorization bypass in REST API Quick Setup endpoints.

Recommended fix High confidence

2.4.0p25 or 2.5.0b2 or later

  1. Verify current Checkmk version by checking the About page or using the command 'cmk --version'
  2. Review the Checkmk upgrade documentation for your specific version at docs.checkmk.com
  3. Create a full backup of the Checkmk site including configuration and database
  4. Stop the Checkmk site before upgrade using 'cmk -S' or site management interface
  5. Download the fixed version (2.4.0p25 or later for 2.4.x, 2.5.0b2 or later for 2.5.x) from the official Checkmk download page
  6. Install the update using the Checkmk package installer for your platform
  7. Start the Checkmk site and verify the upgrade completed successfully using 'cmk -V'
  8. Test REST API Quick Setup endpoints with both privileged and low-privileged accounts to confirm the vulnerability is remediated
Caveat Review Checkmk release notes for any breaking changes between your current version and the target version, particularly regarding REST API behavior and permissions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Checkmk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24096 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24096 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data