dbcve.org
CheckmkApplication

CVE-2025-64997

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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 versions prior to 2.4.0p17 and 2.3.0p42 allow low-privileged users to view agent information via the REST API, which could lead to 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 bypass authorization checks and view agent information that should be restricted to higher-privileged users. This is an information disclosure vulnerability stemming from missing or inadequate access control enforcement on specific API endpoints.

MitigationUpgrade Checkmk to version 2.4.0p17 or 2.3.0p42 or later, which includes proper permission validation for the affected REST API 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.2.0= 2.3.0= 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Identify Checkmk version
    Check the installed Checkmk version using the version command or web interface. Common methods: 'cmk --version' or check the About section in the web UI.
    Affected if Running version 2.2.0, 2.3.0, or 2.4.0 (prior to respective patch releases)
  2. Verify REST API is enabled
    Check if the Checkmk REST API is enabled in the site configuration. Access the web UI, navigate to Setup > General > API and verify the REST API is activated.
    Affected if REST API is enabled and accessible on the Checkmk instance
  3. Identify low-privileged API users
    List users with API access permissions by reviewing user roles in Setup > Users > Users. Look for users assigned to roles with limited permissions (e.g., 'Guest', 'User' roles).
    Affected if Low-privileged users exist with API access credentials
  4. Test endpoint authorization
    Using a low-privileged API user's credentials, attempt to query REST API endpoints related to agent information (e.g., endpoints under /domain-types/agent or /objects/agent). Compare accessible endpoints against what should be restricted based on user role.
    Affected if Low-privileged users can retrieve agent information endpoints that should require higher privileges (admin or inspector roles)

A Checkmk instance is affected if it runs version 2.2.0, 2.3.0, or 2.4.0, has REST API enabled, and permits low-privileged users to access agent information endpoints that should be restricted to higher-privileged roles.

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 Checkmk to version 2.4.0p17 or 2.3.0p42 or later, which includes proper permission validation for the affected REST API endpoints.

Recommended fix High confidence

2.4.0p17 (or 2.3.0p42 for legacy 2.3.x deployments)

  1. Identify current Checkmk version by running 'cmk --version' or checking the GUI
  2. Backup the Checkmk configuration directory (typically /omd/sites/<sitename>/etc/checkmk)
  3. For Checkmk 2.4.0.x: Upgrade to version 2.4.0p17 or later
  4. For Checkmk 2.3.0.x: Upgrade to version 2.3.0p42 or later
  5. For Checkmk 2.2.0.x: Upgrade to 2.3.0p42 or 2.4.0p17 as 2.2.0 is end-of-life
  6. Follow standard Checkmk upgrade procedure: stop site, run 'omd update <sitename>', start site
  7. Verify the upgrade completed successfully and test REST API permission behavior
Caveat Standard Checkmk patch upgrade; review release notes for any configuration changes

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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