dbcve.org
CheckmkApplication

CVE-2025-1712

HIGH · 8.8 CVSS v3.1 Published 2025-05-21
Fix available
A fix is available. Upgrade to 2.2.0 or later.
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
Argument injection in special agent configuration in Checkmk <2.4.0p1, <2.3.0p32, <2.2.0p42 and 2.1.0 allows authenticated attackers to write arbitrary files

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

Argument injection vulnerability in Checkmk's special agent configuration allows authenticated attackers to inject arbitrary arguments that result in writing arbitrary files to the filesystem. The vulnerability stems from insufficient input validation/sanitization in how special agent parameters are processed.

MitigationUpgrade Checkmk to version 2.4.0p1, 2.3.0p32, 2.2.0p42 or later. For unpatched versions, restrict special agent configuration permissions to trusted administrators only as a temporary measure.

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.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
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. Check the installed Checkmk version
    Run 'cmk --version' or check the version through the web interface at 'About Checkmk' in the sidebar. Compare the version number against the affected ranges: any version < 2.2.0, or exactly 2.2.0, 2.3.0, or 2.4.0.
    Affected if The installed version is any release of 2.2.0, 2.3.0, or 2.4.0 (without patch level p42/p32/p1 respectively), or any version below 2.2.0.
  2. Verify if special agents are configured
    Navigate to Setup > Agents > VM, Cloud, Container > Checkmk Agent or check for any configured special agents in the web interface under the relevant special agent configuration pages.
    Affected if Special agent configurations exist and are actively used or enabled.
  3. Identify users with special agent configuration permissions
    Check user role permissions in Setup > Users > Roles or through the command line by examining ~/etc/check_mk/conf.d/ and ~/var/check_mk/reports/ directories for custom special agent configurations.
    Affected if Non-admin users or untrusted accounts have permissions to create or modify special agent configurations.

You are affected if your Checkmk version is 2.2.0, 2.3.0, 2.4.0 or any version below 2.2.0, and special agent configurations can be modified by users who should not have write access to arbitrary files.

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
Upgrade available Upgrade to 2.2.0 or later
Fixed in 2.2.0
Interim mitigation

Upgrade Checkmk to version 2.4.0p1, 2.3.0p32, 2.2.0p42 or later. For unpatched versions, restrict special agent configuration permissions to trusted administrators only as a temporary measure.

Recommended fix High confidence

Upgrade to Checkmk 2.4.0p1 (or later 2.4.x), or 2.3.0p32 (or later 2.3.x), or 2.2.0p42 (or later 2.2.x) depending on your current branch

  1. 1. Identify the current Checkmk version in use by checking the installation or the web interface (About section)
  2. 2. Based on the current version branch, plan the upgrade: For 2.4.x branch, upgrade to version 2.4.0p1 or later; For 2.3.x branch, upgrade to version 2.3.0p32 or later; For 2.2.x branch, upgrade to version 2.2.0p42 or later
  3. 3. Review Checkmk upgrade documentation for your specific deployment type (raw, free, or enterprise edition)
  4. 4. Create a backup of the Checkmk installation and configuration before proceeding with the upgrade
  5. 5. Perform the upgrade following Checkmk's standard upgrade procedure
  6. 6. After upgrade, verify the special agent configuration functionality works correctly
  7. 7. Confirm the version has been updated successfully via the About section in the web interface
Caveat Checkmk upgrades may require testing in a non-production environment first due to potential changes in configuration syntax or feature behavior

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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