dbcve.org
CheckmkApplication

CVE-2025-58122

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/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
Insufficient permission validation in Checkmk 2.4.0 before version 2.4.0p16 allows low-privileged users to modify notification parameters via the REST API, which could lead to unauthorized actions or information disclosure.

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 in Checkmk's REST API allows authenticated low-privileged users to modify notification parameters they should not have access to. This is a broken access control vulnerability where the API fails to enforce proper authorization checks before allowing modifications to notification settings, potentially enabling unauthorized actions or information disclosure.

MitigationUpgrade to Checkmk version 2.4.0p16 or later to obtain the security fix. Until then, restrict low-privileged users' API access and monitor for unauthorized notification configuration changes.

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

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
Low
Integrity
Low
Availability
None

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

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 installed Checkmk version
    Run 'cmk --version' or check the Checkmk web interface footer for the exact version number
    Affected if Version is exactly 2.4.0 (without any patch level like p1-p15)
  2. Verify REST API is enabled
    Check Checkmk configuration files (typically /omd/sites/<site>/etc/check_mk/conf.d/wato.mk or via web UI: Setup > General > API) for 'enable_RESTful_API' setting
    Affected if REST API is enabled and accessible
  3. Identify low-privileged users with API access
    Query the Checkmk user database via 'omd config show' or check Users > Properties in the web UI for users with roles other than 'admin' who have API permissions granted
    Affected if Non-admin users exist with API access permissions
  4. Test notification configuration access for low-privileged users
    Use the REST API endpoint GET/POST /domain-types/notification_config to attempt retrieving or modifying notification parameters using a low-privileged user's API credentials
    Affected if Low-privileged users can read or modify notification settings they should not access

You are affected if your Checkmk version is exactly 2.4.0 (without a patch like p16 or later), the REST API is enabled, and low-privileged (non-admin) users have API access that allows them to modify notification configuration.

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 version 2.4.0p16 or later to obtain the security fix. Until then, restrict low-privileged users' API access and monitor for unauthorized notification configuration changes.

Recommended fix Moderate confidence

2.4.0p16

  1. 1. Back up your Checkmk instance and configuration data before upgrading.
  2. 2. Download Checkmk version 2.4.0p16 from the official Checkmk download page (checkmk.com).
  3. 3. Stop the Checkmk site(s) that need to be upgraded using the command 'omd stop <sitename>'.
  4. 4. Install the new Checkmk package using the appropriate package manager for your system (deb, rpm, or tgz).
  5. 5. Start the Checkmk site using 'omd start <sitename>'.
  6. 6. Verify the upgrade was successful by checking the version with 'omd version <sitename>' or via the web interface.
Caveat Review Checkmk 2.4.0p16 release notes for any configuration changes or migration requirements before upgrading.

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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