dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-24095

MEDIUM · 5.3 CVSS v4.0 Published 2026-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
Improper permission enforcement in Checkmk versions 2.4.0 before 2.4.0p21, 2.3.0 before 2.3.0p43, and 2.2.0 (EOL) allows users with the "Use WATO" permission to access the "Analyze configuration" page by directly navigating to its URL, bypassing the intended "Access analyze configuration" permission check. If these users also have the "Make changes, perform actions" permission, they can perform unauthorized actions such as disabling checks or acknowledging results.

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

Checkmk versions prior to 2.4.0p21 and 2.3.0p43 contain an improper permission enforcement vulnerability where the 'Analyze configuration' page only performs authorization checks when accessed through the UI navigation, but not when directly navigated to via URL. Users with 'Use WATO' permission can bypass the required 'Access analyze configuration' permission, and if they also possess 'Make changes, perform actions' permission, they can perform unauthorized administrative actions such as disabling checks or acknowledging results.

MitigationUpgrade to Checkmk versions 2.4.0p21, 2.3.0p43 or later. Until patched, monitor access logs for unauthorized access to the Analyze configuration URL paths and restrict the 'Use WATO' permission to only trusted administrators.

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

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Check the installed Checkmk version
    Run the Checkmk version command (e.g., 'omd version' or check the About section in the UI) and note the exact version number
    Affected if The version is below 2.4.0p21 or below 2.3.0p43 (or is a version other than 2.3.x or 2.4.x and is older than those patch levels)
  2. Verify user permissions configuration
    Access the Checkmk user/role administration and list which users or roles have the 'Use WATO' permission assigned
    Affected if Any user account has 'Use WATO' permission enabled
  3. Check for combined permissions on any user
    In the same user/role administration, identify if any user possessing 'Use WATO' also has the 'Make changes, perform actions' permission
    Affected if A single user account has both 'Use WATO' AND 'Make changes, perform actions' permissions simultaneously
  4. Review access logs for Analyze configuration URL access
    Search the web server or Checkmk access logs for direct requests to the Analyze configuration URL path (typically contains 'analyze' or 'analyse' in the path, often under the wato endpoint)
    Affected if Access logs show requests to the Analyze configuration URL from users who lack the explicit 'Access analyze configuration' permission

You are affected if your Checkmk version is below 2.4.0p21 or 2.3.0p43 AND any user has the 'Use WATO' permission (especially if combined with 'Make changes, perform actions').

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

Upgrade to Checkmk versions 2.4.0p21, 2.3.0p43 or later. Until patched, monitor access logs for unauthorized access to the Analyze configuration URL paths and restrict the 'Use WATO' permission to only trusted administrators.

Recommended fix High confidence

2.4.0p21 (or later) for 2.4.x branch; 2.3.0p43 (or later) for 2.3.x branch; 2.2.0 is EOL with no fix, migrate to 2.3.x or 2.4.x

  1. Identify the current Checkmk version by checking the version info in the web interface or command line
  2. If running 2.2.0: This version is End-of-Life (EOL) with no patch available; plan migration to a supported branch (2.3.x or 2.4.x)
  3. If running 2.4.0 before 2.4.0p21: Upgrade to version 2.4.0p21 or later
  4. If running 2.3.0 before 2.3.0p43: Upgrade to version 2.3.0p43 or later
  5. After upgrading, verify that the "Access analyze configuration" permission is properly enforced when users try to access the Analyze configuration page directly via URL
  6. Confirm users without the required permission can no longer bypass the authorization check
Caveat 2.2.0 is End-of-Life (EOL) - no security patches available; users must migrate to a supported branch. Review Checkmk migration guides when moving between major versions.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24095 — 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-24095 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